Odd memory consumption between x32 and x64

 

I've been profiling the x64 version of my application as the memory usage has been outrageously high, all of it seems to be coming from the JavaFX MediaPlayer, i'm correctly releasing listeners and eventhandlers.

Here is the stark contrast.

The x32 version at start

And now the x64 version at start

The x32 version stays below 256mb while the x64 will shoot over a gig; this is while both are left to play through their playlist.

All the code is the same.

JDK: jdk1.8.0_20

JRE: jre1.8.0_20

VM arguments on both 

-XX:MinHeapFreeRatio=40 -XX:MaxHeapFreeRatio=70 -Xms3670k -Xmx256m -Dsun.java2d.noddraw=true -XX:+UseParallelGC

Same issue occurring on another x64 Java application

Is this a bug or am I overlooking something?

What you are seeing is the memory usage of the entire JVM running your process. The -Xmx256m setting only limits the maximum heap space available for your application to allocate (and the JVM would enforce that). Outside of heap space, the JVM can use additional memory for a host of other purposes (I am sure I will miss a few in the list below):

  • PermGen, which has now be replaced by the Metaspace. According to the documentation, there is no default limit for this: 

    -XX:MaxMetaspaceSize=size
Sets the maximum amount of native memory that can be allocated for class metadata. By default, the size is not 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.

  • Stack space (memory used = (number of threads) * stack size. You can control this with the -Xss parameter

  • Off-heap space (either use of ByteBuffers in your code, or use of third pary libraries like EHCache which would in turn use off-heap memory)

  • JNI code

  • GC (garbage collectors need their own memory, which is again not part of the heap and can vary greatly depending on the collector used and the application memory usage)

    • In your case, you are seeing the "almost doubling" of memory use, plus probably a more relax Metaspace allocation when you move from a 32bit to a 64bit JVM. Using -XX:MaxMetaspaceSize=128m will probably bring the memory usage down to under 512MB for the 64bit JVM.

    I don't know your application, respectively how it is implemented.

    One possible reason for such a surprize differences could be how much memory can be used before a garbage collection is performed. It is thinkable that a machine with 64 bit words is allocated with more memory then a machine with 32 bit words. The garbage collector could run less often, so there would be more garbage memory still allocated, even when it is not really necessary or usefull.

    链接地址: http://www.djcxy.com/p/22936.html

    上一篇: GLSL顶点着色器双线性采样高度图

    下一篇: x32和x64之间的内存消耗量很奇怪