Re: Swap space (was: Re: [Cooker] kdelibs: memory usage: something _must_ be wrong)
Hello, Try running the Together UML tool and the AdventNet SNMP toolkit at the same time. They are both java apps.. We use these at work where we have by default 256Mb RAM and a 128Mb swap partition. I have created a couple of swap files amounting to about 350Mb. These two apps. will easily go over the 256Mb RAM + 128Mb swap when running gnome on Enlightenment on X. Run a couple of emacs, Mozilla (plus Netscape to cope when Moz fails to render or crashes !), gFTP, a couple of Xterms, a couple of gmc's and then kick of StarOffice to complete some documentation which has to be presented in Word .doc format and don't forget all the daemons in the background (smb, nfs etc.) then voila ! Which is why I have an extra 300Mb swapfile(s). I consider this to be lightly loaded for a typical working scenario, dont' you :-) Plus, Linux doesn't handle running out of memory very gracefully. You can get to tell when it's about to happen and, if you act quickly enough, you can save the situation. If you leave it too long your machine will effectively freeze ! So there ! ( ;-) ) Owen On Sun, 01 Oct 2000, you wrote: On Sun, Oct 01, 2000 at 09:56:57PM +0200, Stefan van der Eijk wrote: You _must_ be kidding!!! 512Mb + 256 swap (yeah yeah, 256Mb swap is too small, but for a box that normally only has 128Mb it's fine) is clearly Sorry? How loaded is your box? Normally 256 MB for swap is way more than enough. I get around here perfectly fine with 128 MB of swap, and the swap normally isn't even half full. Sure, I'm the only one at my machine, besides some sporadic ftp/http users, but for that kind of use (which includes compiling) more isn't needed. Alexander Skwar -- Homepage: http://www.digitalprojects.com | http://www.dp.ath.cx Sichere Mail? Mail an [EMAIL PROTECTED] fuer GnuPG Keys ICQ: 7328191
Re: [Cooker] kdelibs: memory usage: something _must_ be wrong
Stefan van der Eijk [EMAIL PROTECTED] writes: [...] What frightens me is that one day I'm going to compile kdelibs on my alpha (if Troll ever gets qt2 ported to _modern_ alpha system, not a 2 year old RedHat 5.2). What's going to happen then? Alpha's are a bit more memory hungry than x86, good chance it might even starve Mandrake's 1Gb alpha box. Alpha opts are currently set up to -O2 maybe this will not fail :-). Is it rediculous to ask the following: which specifications must the machine of a developper (or idiot that tries to help) be? Shouldn't 128Mb in an x86 box be enough nowadays? How much does the -O3 help speedup kdelibs over an -O2 or -O1? Can the "heavy optimalisation" be commented out during development turned on just before release (damn... we're there already, just B4 release...)? Actually you know that optimizition sometimes break out things -- and now that we have real fast machines (when they are up) it's really not a pain to produce highly optimized rpm's. If you don't want them, just modify /usr/lib/rpm/rpmrc according to your needs. Removing the -O stuff will lead to real fast (and succesful hopefully) builds.. -- Guillaume Cottenceau -- Distribution Developer for MandrakeSoft http://www.mandrakesoft.com/~gc/
Re: [Cooker] kdelibs: memory usage: something _must_ be wrong
Stefan van der Eijk [EMAIL PROTECTED] writes: Hmmm... My intel box just started compiling the latest kdelibs when all of a sudden everything slowed down. And I mean EVERYTHING. The compiler had "taken" 92% of the memory in the box (I've moved the 512Mb from my alpha to my intel, for testing, it didn't work nice in my alpha). Here's the output: make[3]: Entering directory `/data/users/cooker/RPM/BUILD/kdelibs/arts/mcopidl' g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../dcop -I../../kdecore -I../../kdeui -I../../kssl -I/usr/lib/qt2/include -I/usr/X11R6/include -I/usr/include -I./../mcop-O3 -fomit-frame-pointer -pipe -s -march=pentium -ffast-math -fexpensive-optimizations -DNDEBUG -frtti -c mcopidl.cc mcopidl.cc: In function `class string createTypeCode(basic_stringchar,string_char_traitschar,__default_alloc_templatetrue,0 , const string , long int, basic_stringchar,string_char_traitschar,__default_alloc_templatetrue,0 = "")': mcopidl.cc:688: virtual memory exhausted Is this normal? What kind of box do you need to be able to compile this No :-)).. Usually this happens when optimization levels is too high considered complexity of the task involved for optimizing and available memory. If you remove "-O3" from the compile line it will certainly work -- well ok this is not a valid fix considered specfile/rpm building but.. -- Guillaume Cottenceau -- Distribution Developer for MandrakeSoft http://www.mandrakesoft.com/~gc/
Re: [Cooker] kdelibs: memory usage: something _must_ be wrong
mcopidl.cc:688: virtual memory exhausted Is this normal? What kind of box do you need to be able to compile this No :-)).. Thank god!! Usually this happens when optimization levels is too high considered complexity of the task involved for optimizing and available memory. Sounds logical... If you remove "-O3" from the compile line it will certainly work -- well ok this is not a valid fix considered specfile/rpm building but.. This is now the 2nd package that does this with me. Mysql on the alpha also eats up everything it can get. With 128Mb in my alpha it will crash the machine or make it useless -- starving mem out of daemons, etc. 512Mb of mem is enough, it completes without swapping too much. Mysql only does this on my alpha, on my x86 (normally 128Mb) it compiles fine. What frightens me is that one day I'm going to compile kdelibs on my alpha (if Troll ever gets qt2 ported to _modern_ alpha system, not a 2 year old RedHat 5.2). What's going to happen then? Alpha's are a bit more memory hungry than x86, good chance it might even starve Mandrake's 1Gb alpha box. Is it rediculous to ask the following: which specifications must the machine of a developper (or idiot that tries to help) be? Shouldn't 128Mb in an x86 box be enough nowadays? How much does the -O3 help speedup kdelibs over an -O2 or -O1? Can the "heavy optimalisation" be commented out during development turned on just before release (damn... we're there already, just B4 release...)? Stefan
Re: [Cooker] kdelibs: memory usage: something _must_ be wrong
Also sprach Stefan van der Eijk : Is this normal? What kind of box do you need to be able to compile this stuff? A 2Gb quad Xeon "I normally simulate nucular blasts in office ^^ hours, but in the evenings I compile kdelibs-1.94-14mdk" kind of box? ^ In what precise kind of office are you working, Stefan :-) ? -- Guillaume Rousse Murphy's law : If anything can go wrong, it will. O'Tool's commentary : Murphy was an optimist.
Re: [Cooker] kdelibs: memory usage: something _must_ be wrong
Is this normal? What kind of box do you need to be able to compile this stuff? A 2Gb quad Xeon "I normally simulate nucular blasts in office ^^ hours, but in the evenings I compile kdelibs-1.94-14mdk" kind of box? ^ In what precise kind of office are you working, Stefan :-) ? You don't want to know ;-) But... we _don't_ simulate nuclear blasts (or anything like that), nor do we have a spare 2Gb machine lying around... Stefan
Swap space (was: Re: [Cooker] kdelibs: memory usage: something _must_ be wrong)
On Sun, Oct 01, 2000 at 09:56:57PM +0200, Stefan van der Eijk wrote: You _must_ be kidding!!! 512Mb + 256 swap (yeah yeah, 256Mb swap is too small, but for a box that normally only has 128Mb it's fine) is clearly Sorry? How loaded is your box? Normally 256 MB for swap is way more than enough. I get around here perfectly fine with 128 MB of swap, and the swap normally isn't even half full. Sure, I'm the only one at my machine, besides some sporadic ftp/http users, but for that kind of use (which includes compiling) more isn't needed. Alexander Skwar -- Homepage: http://www.digitalprojects.com | http://www.dp.ath.cx Sichere Mail? Mail an [EMAIL PROTECTED] fuer GnuPG Keys ICQ:7328191
Re: [Cooker] kdelibs: memory usage: something _must_ be wrong
On Sun, Oct 01, 2000 at 10:09:00PM +0200, Stefan van der Eijk wrote: do we have a spare 2Gb machine lying around... No? How lame *g* If your company doesn't pay you enough for such a "toy", you are really underpaid :-))) SCNR Alexander Skwar -- Homepage: http://www.digitalprojects.com | http://www.dp.ath.cx Sichere Mail? Mail an [EMAIL PROTECTED] fuer GnuPG Keys ICQ:7328191
Re: Swap space (was: Re: [Cooker] kdelibs: memory usage: something _must_ be wrong)
You _must_ be kidding!!! 512Mb + 256 swap (yeah yeah, 256Mb swap is too small, but for a box that normally only has 128Mb it's fine) is clearly Sorry? How loaded is your box? Normally 256 MB for swap is way more than enough. I get around here perfectly fine with 128 MB of swap, and the swap normally isn't even half full. Sure, I'm the only one at my machine, besides some sporadic ftp/http users, but for that kind of use (which includes compiling) more isn't needed. Try compiling the current kdelibs... you'll be surprised (I was!). Stefan
