Dawn of the Geeks

Apache2.2 was having the same problems as Apache2.0 minus the unexplained crash.  Memory was still being consumed in large quantities and it would become unresponsive.  Turns out that eAccelerator was still being loaded and some alternate cache thing was also being loaded.

I removed those and it seems to be working fine now.  eAccelerator is pretty much garbage.  I tried it out when I was developing Bunnies because that site is quite complex.  I had disabled it thinking that would be fine but no, it had to be removed entirely.  It came to my attention because I upgraded to PHP 5.2.5 and eAccelerator was throwing an error.

It’s gone now and the memory usage is staying more consistant.  The site also runs fine.  The big reason for looking for accelerators a long time ago was that many of my sites were running on a PIII 933 Mhz system.  They’re now running on a Dual Core 1.6Ghz system.