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
