Hemmann, Volker Armin posted <[EMAIL PROTECTED]>, excerpted below, on Wed, 25 Jan 2006 18:16:33 +0100:
> On Wednesday 25 January 2006 17:59, Daniel Gryniewicz wrote: > >> >> I build with -j5 and 1GB of ram. If it ooms for you, you have a broken >> kernel, get a better one. (I use ck-sources, and have never seen an OOM >> of any variety) > > I used a wide array of kernels. > > OOM is easy: > compile kde-base or kdelibs with kdeenablefinal or wesnoth. With a gig of physical memory here, and swap entirely turned off for some time, my issues weren't with kdebase or kdelibs, but with kdepim, before the spit ebuilds, or kmail, since them. With USE=kdeenablefinal, there's one spot in the kmail build that takes over 700MB for a single build-thread! I watched as the single thread gobbled that much, in top. I have swap reenabled now, four, 4-gig partitions, each on a separate SATA drive, set at the same swap-priority, thus giving me 16-gig of 4-way striped swap, which seems to work quite well along with my 4-drive RAID-6 (thus two-way striped) main system and 4-way striped RAID-0 /tmp, /var/tmp, ccachedir, and the like, all running on separate partitions of the same 4-drive SATA set (300 gig Seagates). Now, I regularly run upto five separate emerges at the same time, each with -j3, in ordered to keep both Opteron 242s busy. I can even do that with one of them being kmail, without issue now, all while continuing to run X with my existing KDE, and PAN and my existing kmail, without serious UI slowdown. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
