JDK-7012344 : Massive memory/process size increases in recent java releases
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6u23
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: linux_redhat_5.0
  • CPU: x86
  • Submitted: 2011-01-14
  • Updated: 2012-03-20
  • Resolved: 2011-02-02
Related Reports
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Linux drill.jpl.nasa.gov 2.6.18-194.11.1.el5PAE #1 SMP Tue Jul 27 06:02:35 EDT 2010 i686 i686 i386 GNU/Linux


A DESCRIPTION OF THE PROBLEM :
When we went from build 17 to build 20, the size of all our Java processes and their associated heaps DOUBLED.  Build 23 does not fix the problem.

jconsole heap size in build 17 was 300MB.
jconsole heap size in build 20 is 600MB.
jconsole heap size in build 23 could not be measured because the darned thing won't even connect to jconsole.

process size in build 17 was 500MB.
process size in build 20 is 1.1GB.

This is the same code, doing the same thing, all compiled with build 20.

This is absolutely killing us.  What happened? Did the garbage collection change in some way?



REPRODUCIBILITY :
This bug can be reproduced always.

Comments
EVALUATION This was due to ergonomics changes. crocker% bin/java -XX:+PrintCommandLineFlags -version -XX:MaxHeapSize=792795136 -XX:ParallelGCThreads=4 -XX:+PrintCommandLineFlags -XX:+UseParallelGC java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) Server VM (build 14.3-b01, mixed mode) crocker% cd ../../6u20/jdk*20 crocker% bin/java -XX:+PrintCommandLineFlags -version -XX:InitialHeapSize=49549696 -XX:MaxHeapSize=792795136 -XX:ParallelGCThreads=4 -XX:+PrintCommandLineFlags -XX:+UseParallelGC java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode) The InitialHeapSize was increased. See bug 6887571. You can specify -Xms to return to the old heap size if necessary. This affect was intentional.
02-02-2011