![]() ![]() ![]() There are some details here ( ) and other places. So it could also be that the perm space on Suse has a larget default than on Redhat.Īlso, depending on the memory allocation profile of your application, you might get away with a smaller heap size and different garbage collecting options. The other memory settings also affect the size of your heap (like permgen). I don't know the particulars of where Redhat or Suse load stuff into memory, but it could be that suse is mapping some library to an address in the middle of RAM, where Redhat might map it at the end (speculating).Īnd remember that your actual memory usage in java is more than what you specify for Xmx. The limit varies from about 1.4 GB to a bit over 2.0 GB, and depends on where your operating system puts various things in memory. The JVM memory limit is related the largest free contiguous block available, not the amount of free memory.
0 Comments
Leave a Reply. |