The application has a heap of 8gb and creates a lot of short living objects You have distinct categories of jvm arguments I noticed that it often paused for some seconds to do garbage collection
@xx.curlzzz.xx | Bad b*tch status every time I pop out οΈπ | Instagram
Sizes are expressed in bytes
Append the letter k or k to indicate kilobytes, m or m to indicate megabytes, g or g to indicate gigabytes
How is the java memory pool divided? Since we are getting java.lang.outofmemoryerror By default, the size isn't limited The amount of metadata for an application depends on the application itself, other running applications, and the amount of memory available on the system.
The x's represent numbers only And total number of dashes is either 2 or 1. As already noted, this helps size thread pools but does not impose any hard limit on the number of cpu cores that can be used. Do you load many different classes dynamically
Then you could maybe define a free ratio on the metaspace so that always enough space for new classes is available and no resizing will be needed in critical situations.
