» Find Revision
L2J Revision Number: 3430
L2JDP Revision Number: 6537
I have read a lot of info about JVM , heap sizes and general config...still, the one thing i don t understand is
why the JV after increases to the max size (xmx) doesen`t decrease , cleaning up garbage using (xmn) but gives errors in game console and eats up the cpu instead of freeing up the java app used memory when it reaches the max value, also many functions in game seize to function
this is my startup.bat
Code: Select all
java -server -Xmx2048m -Xms2048m -Xmn512m -XX:PermSize=256m -XX:SurvivorRatio=8 -Xnoclassgc -XX:+AggressiveOpts -cp ./../libs/*;l2jserver.jar net.sf.l2j.gameserver.GameServer
-Xms<size>
Specifies the initial size of the committed memory within the Java™ heap. It also specifies the minimum size of the committed area. The value must be a multiple of 1024 greater than 1MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.
For example, -Xms6291456, -Xms6144k, -Xms1500M
-Xmx<size>
Specifies the maximum size of the Java™ heap. The value must a multiple of 1024 greater than 2MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.
For example, -Xmx83886080, -Xmx81920k, -Xmx1500M
You will notice the increased memory footprint described in the previous section most if you set -Xms to the same value as -Xmx. This is because the whole of the associated heap spaces are committed and the JVM reserves swap for them by touching every page. In this case it would be better to use the -XX:+ForceMmapReserved option because it is more efficient.
( i have it 512).Due to the design of HP-UX, the heap is not one contiguous mmap. When the heap is getting this large, either the new space, set with -Xmn, or old space, set by the difference of Xmx and Xmn, must be 900MB or less