java - JVM performance with these garbage collection settings -
I have an enterprise-level Java application that makes a few thousand users per day on this weblogic 10.3.6 (Java 1.6 JVM) There is a JACAB web service, using hibernate to hit an Oracle database. It also calls other web services.
We see the following GC settings on our production system:
-server -Xms2048m -Xmx2048m -XX: PermSize = 512m - XX: MaxPrimisize = 512m < / Code> What is the effect of this GC sizing? The hardware has more than enough capacity to handle it.
I know that it sets stack size and paragraph general at a steady level, but what is the effect of it when you finally have to store garbage?
It seems to me that this happens less often, but it takes more time to happen. Is it true?
It happens less often, but it takes longer when it can be done < / P>
It may happen, it depends on the case of your use. You can also see that GC is less in the rare case.
A 2 GB pile is not so much and I will use up to 26 GB without worrying about the size of the pile. This size is slightly slower than memory access or more memory is used.
Comments
Post a Comment