Plain 2.4.5 VM...
Ouch! When compiling MySql, building sql_yacc.cc results in a ~300M cc1plus process size. Unfortunately this leads the machine with 380M of RAM deeply into swap:
Mem: 381608K av, 248504K used, 133104K free, 0K shrd, 192K
buff
Swap: 255608K av, 255608K used, 0K free 215744K
cached
Vanilla 2.4.5 VM.
Signature · 3 lines
Jeff Garzik | Disbelief, that's why you fail. Building 1024 | MandrakeSoft |
Quoted 11 lines · Jeff Garzik
Ouch! When compiling MySql, building sql_yacc.cc results in a ~300M cc1plus process size. Unfortunately this leads the machine with 380M of RAM deeply into swap:
Mem: 381608K av, 248504K used, 133104K free, 0K shrd, 192K
buff
Swap: 255608K av, 255608K used, 0K free 215744K
cachedVanilla 2.4.5 VM.
I don't think this is new/unusual.
You can add the following to configure when compiling mysql ..
--with-low-memory Try to use less memory to compile to avoid
memory limitations.
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
[email protected]
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
[email protected]
=====================================================================
Quoted 5 lines · Jeff Garzik
Ouch! When compiling MySql, building sql_yacc.cc results in a ~300M cc1plus process size. Unfortunately this leads the machine with 380M of RAM deeply into swap:
Quoted 7 lines
Mem: 381608K av, 248504K used, 133104K free, 0K shrd, 192K
buff
Swap: 255608K av, 255608K used, 0K free 215744K
cachedVanilla 2.4.5 VM.
Sorry. I just looked at your numbers again and saw you have 133 MB of real ram free. Is this during compile?
Signature · 8 lines
=====================================================================
Mohammad A. Haque http://www.haque.net/
[email protected]
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
[email protected]
=====================================================================Quoted 8 lines
Ouch! When compiling MySql, building sql_yacc.cc results in a ~300M cc1plus process size. Unfortunately this leads the machine with 380M of RAM deeply into swap:
Mem: 381608K av, 248504K used, 133104K free, 0K shrd, 192K
buff
Swap: 255608K av, 255608K used, 0K free 215744K
cached
That is supposed to hapen. The pages are existing both in swap and memory but not recovered. In that state the VM hasn't even broken yet.
Where you hit a problem is that the 255Mb of stuff both in memory and swap won't be flushed from swap when you need more swap space. That is a giant size special edition stupid design flaw that is on the VM hackers list. But there are only a finite number of patches you can do in a day, and things like sucking completely came first I believe