Um, this is not a problem, your memory looks fine. What makes you think the metaspace usage is a problem?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi.because is seems full.we are using jira service desk in an enterprise company and I was wondering if there would be a problem in the future related to the memory space.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The JVM is at 65%, which seems pretty reasonable?
The spaces shown below, like PS Surviror Space or MetaSpace which are at 0%, you don't need to worry about them.
It's the expected behavior.
Although if you are experiencing slow performance and JVM keeps running out, then you can increase it further.
But I think its working fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your response.you mean that there is no worry for the spaces which is shown as full?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, no need to worry about it. This is because your MetaSpace argument is not configured.
You can refer to this KB: https://confluence.atlassian.com/jirakb/the-jira-applications-memory-information-screen-displays-0-free-metaspace-873885725.html
And you don't need to worry about Eden Space either. Because on creation of objects, they are allocated some memory in Eden Space and when the Eden Space gets full, it triggers a minor garbage collection where objects are either destroyed or moved to a Survivor Space.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.