Bug#519012: openjdk-6: Requests upto 18 GB of RAM during build

2009-03-16 Thread Matthias Klose 
which architecture is this?
which processes are left for which target (stage1 build, stage2 build, alternate
zero build, alternate cacao build, running the testsuite)?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#519012: openjdk-6: Requests upto 18 GB of RAM during build

2009-03-16 Thread Kurt Roeckx 
On Mon, Mar 16, 2009 at 08:51:02AM +0100, Matthias Klose wrote:
 which architecture is this?

amd64

 which processes are left for which target (stage1 build, stage2 build, 
 alternate
 zero build, alternate cacao build, running the testsuite)?

During the build it looked like this:
buildd   28568  0.1  0.7 1016204 15708 ?   Sl   10:51   0:00 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/jre/bin/java
 sun.rmi.registry.RegistryImpl 17340
buildd   27812  0.1  0.9 1023576 19876 ?   Sl   10:48   0:00 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/jre/bin/java
 
-Djava.util.logging.config.file=/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/jdk/test/sun/rmi/runtime/Log/6409194/logging.properties
 NoConsoleOutput$DoRMIStuff
buildd   23134  0.0  1.1 1023516 23684 ?   Sl   10:34   0:01 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/bin/java
 -Dsun.net.spi.namservice.provider.1=dns,sun TestApplication
buildd   23089  0.0  1.1 1023512 23672 ?   Sl   10:34   0:01 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/bin/java
 TestApplication
buildd   23058  0.0  1.1 1022636 23288 ?   Sl   10:34   0:00 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/bin/java
 
-javaagent:/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/jre/lib/management-agent.jar
 TestApplication
buildd   23021  0.0  1.0 1020148 21424 ?   Sl   10:33   0:01 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/bin/java
 -Dcom.sun.management.jmxremote TestApplication
buildd   19044  0.0  0.9 1025232 20588 ?   Sl   08:52   0:03 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/bin/java
 -server -cp 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/test/jdk/JTwork/classes/java/rmi/reliability/benchmark
 
-Djava.security.policy=/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/jdk/test/java/rmi/reliability/benchmark/bench/rmi/policy.all
 bench.rmi.Main -server 2007 -c 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/jdk/test/java/rmi/reliability/benchmark/bench/rmi/config
buildd   18375  0.0  1.0 1028560 21100 ?   Sl   08:49   0:03 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/jre/bin/java
 RegistryRunner 2006
buildd   13136  0.0  1.0 1024560 21068 ?   Sl   08:29   0:04 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/jre/bin/java
 
-Djava.security.policy=/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/jdk/test/java/rmi/activation/Activatable/checkActivateRef/rmid.security.policy
 -Dsun.rmi.server.activation.debugExec=true 
-Dtest.src=/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/jdk/test/java/rmi/activation/Activatable/checkActivateRef
 
-Dtest.classes=/build/buildd/openjdk-6-6b14-1.5~pre1/build/test/jdk/JTwork/classes/java/rmi/activation/Activatable/checkActivateRef
 -Djava.rmi.server.logLevel=v sun.rmi.server.Activation -log 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/test/jdk/JTwork/scratch/./log -port 
1098 
-C-Dtest.src=/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/jdk/test/java/rmi/activation/Activatable/checkActivateRef
 
-C-Dtest.classes=/build/buildd/openjdk-6-6b14-1.5~pre1/build/test/jdk/JTwork/classes/java/rmi/activation/Activatable/checkActivateRef
buildd   31756  0.0  0.5 1015612 11932 ?   Sl   07:33   0:05 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/bin/java
 
-Xbootclasspath:/build/buildd/openjdk-6-6b14-1.5~pre1/build/test/jdk/JTwork/classes/java/net/DatagramSocket/SetDatagramSocketImplFactory:/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/lib/classes.zip:/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/jre/lib/rt.jar:/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/classes
 ADatagramSocket true
buildd   16832  0.0  0.6 1015756 12396 ?   Sl   06:22   0:07 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/bin/java
 -jar 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/test/jdk/JTwork/classes/com/sun/tools/attach/Application.jar
buildd   16512  0.0  0.8 1085480 18240 ?   Sl   06:20   0:07 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/bin/java
 -Dattach.test=true -jar 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/test/jdk/JTwork/classes/com/sun/tools/attach/Application.jar
buildd   11798  0.0  0.5 967708 11668 ?Sl   06:09   0:00 
/build/buildd/openjdk-6-6b14-1.5~pre1/build/openjdk/control/build/linux-amd64/j2sdk-image/jre/bin/java
 -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=57169 Exit0

Bug#519012: openjdk-6: Requests upto 18 GB of RAM during build.

2009-03-15 Thread Kurt Roeckx 
On Mon, Mar 09, 2009 at 10:15:47PM +0100, Kurt Roeckx wrote:
 Source: openjdk-6
 Version: 6b14-1.5~pre1-3
 
 Hi,
 
 On the buildd I have vm.overcommit_memory set to 2, so restricting 
 the amount of RAM applications can requested to what is available
 of RAM and swap.  The buildd has 2 GB of RAM and 20 GB of swap.
 
 During the build of openjdk-6, the box had 10 GB commited for most
 of the time, with a peak of 19 GB near the end.  But at no time
 anything was really using that much RAM.  Active only showed a
 peak of 1 GB, and the amount of cache was always 1 GB or more.
 
 So it seems this currently wasn't a problem.  But future builds
 might fail instead because memory allocation fails.  It would
 be a good thing if you didn't allocate so much RAM you're never
 going to use.

There is currently an other build log going on.  I currently
see 19 java processes running, each having a virtual size of
1 GB.  Most use about 10-40 MB RAM, 1 uses 200 MB.

I think this issue might be related to #493339 that the process
keep running.


Kurt




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#519012: openjdk-6: Requests upto 18 GB of RAM during build.

2009-03-09 Thread Kurt Roeckx 
Source: openjdk-6
Version: 6b14-1.5~pre1-3

Hi,

On the buildd I have vm.overcommit_memory set to 2, so restricting 
the amount of RAM applications can requested to what is available
of RAM and swap.  The buildd has 2 GB of RAM and 20 GB of swap.

During the build of openjdk-6, the box had 10 GB commited for most
of the time, with a peak of 19 GB near the end.  But at no time
anything was really using that much RAM.  Active only showed a
peak of 1 GB, and the amount of cache was always 1 GB or more.

So it seems this currently wasn't a problem.  But future builds
might fail instead because memory allocation fails.  It would
be a good thing if you didn't allocate so much RAM you're never
going to use.


Kurt




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org