4 ms·
And then my Slicehost 256 catches on fire. Max_clients hit. Working to fix it now. Those EC2 spot instances are looking awfully tasty...
by tibbon 16y ago
And then my Slicehost 256 catches on fire. Max_clients hit. Working to fix it now. Those EC2 spot instances are looking awfully tasty...
- chaosmachine 16y agoIf you haven't already, disable keepalive. It makes all the difference. http://www.kalzumeus.com/2010/06/19/running-apache-on-a-memory-constrained-vps/ http://www.kalzumeus.com/2010/06/19/running-apache-on-a-memo...
- tibbon 16y agoGiving that a shot right now. Just did a hard reset on the slice. Disabled Keepalive. Think I have too many clients set open still. Back up. Thanks for the page link. Saved me there. Keepalive was definitely on. Hmm, its accepting some traffic, but I don't think I can set my max_clients any higher or it all blows up completely.
- wadetandy 16y agoswitch to apache behind nginx!
- xiongchiamiov 16y agoAlthough webserver choices are a matter of much contention, many people have found success in switching to a non-Apache setup on low-resource servers, like your slice. It's my belief that you can get Apache to perform just as well as those, but it takes a lot more tweaking, and most people really aren't that familiar with Apache config options. I personally have been quite happy with Cherokee.