4 ms·
After figuring Shit out, let's hope the author figures out how to scale this website.
by erlanger 17y ago
After figuring Shit out, let's hope the author figures out how to scale this website.
- shalmanese 17y agoI'm at a loss at this point. The server's been hit with higher loads than this and survived fine. It's running Wordpress on Apache on a 512MB slice, there's no reason it should be this slow. Just rebooted it and it's still slow. If you want to help me debug it, my AIM username is the same as my HN one.
- Rabidmonkey1 17y agoCould you post the text of the article here, seeing as the server is down? I, and I'm sure others, haven't had the chance to read it yet...
- deleted 17y ago[deleted]
- gojomo 17y agoMake sure it's not swapping. Protect yourself against CGI-related memory leaks by making MaxRequestsPerChild small but non-zero. Revert any changes you made to various Apache limits (esp. thread or socket related) before the problem began. Turn off any other services. If all else fails, add a redirect to all clients except the CoralCDN itself to the CoralCDN. (See instructions at < http://wiki.coralcdn.org/wiki.php?n=Main.Servers http://wiki.coralcdn.org/wiki.php?n=Main.Servers >.)
- zepolen 17y agolocation /people-are-twice-as-smart-as-they-talk-three-times-as-smart-as-they-write { serve static_article.html }
- swombat 17y agoWordpress should do that by itself... Also, I think he mentioned apache rather than nginx...
- zepolen 17y agoWordpress can't do it by itself, it can't configure the webserver, and if you meant loading and serving the file by itself - it still means using a heavy php process instead letting the webserver serve a few bytes of disk (which they are always great at doing). Yea I saw he was using apache, but I thought I may as well try to lead him to the dark side :)