chris burgess wrote: > I'd really appreciate any suggestions / input. (Open to commercial support > offers too, of course.)
I've used and still use eAccelerator for a few years on a fairly busy non-commercial site (around 14 million pages served per month) with under resourced hardware (an early g4 mac mini) and had no segfault problems. OS X's periodic/daily scripts do a graceful on apache each night right after log rotation which I haven't really questioned. I have MaxRequestsPerChild in httpd.conf set to 5000. My eaccellerator config is fairly standard: eaccelerator.shm_size = "0" eaccelerator.cache_dir = "/var/cache/eaccelerator" eaccelerator.enable = "1" eaccelerator.optimizer = "1" eaccelerator.debug = 0 eaccelerator.name_space = "" eaccelerator.check_mtime = "1" eaccelerator.filter = "" eaccelerator.shm_max = "0" eaccelerator.shm_ttl = "0" eaccelerator.shm_prune_period = "0" eaccelerator.shm_only = "0" eaccelerator.compress = "1" eaccelerator.compress_level = "9" eaccelerator.keys = "shm_and_disk" eaccelerator.sessions = "shm_and_disk" eaccelerator.content = "shm_and_disk" eaccelerator.allowed_admin_path = "" Personally I've found targeted database tuning can make massive performance increases. MySQL examples ahead. Utilising the slow query log in MySQL to find slow queries and optimising from there, along with checking and fixing your bottlenecks using 'SHOW STATUS;' (turn on query cache if suitable, increasing some of the buffers etc). Good luck. Cheers, Paul --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
