4 ms·

Just a small announce on HN, and the site is down. Why does most blog software fail at simple tasks like delivering static content? Apart from comments and qui

by vog 16y ago

Just a small announce on HN, and the site is down. Why does most blog software fail at simple tasks like delivering static content? Apart from comments and quick corrections, blog articles _are_ nothing more than static content. And I'd be happy to not see any comments due to high server load, as long as I can read the article.

steveklabnik 16y ago
Given the popularity of Wordpress on LAMP, it could be something like KeepAlive: 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...
- bieh 16y ago
  I tried this, the site seems much more responsive now. Thanks!
  - boyter 16y ago
    I did the same thing when searchforphp hit the front page. Before I disabled it the server died under the strain. Following it everything was smooth sailing again.
bieh 16y ago
It's working again now. Although I had to lower the number of maxworkers to get it stable, so it may be slow. And yeah, I'll be investigating why it's so slow tomorrow after the heat dies down. I think this is the first time that wordpress instance has served more than a few hits per day, so I'm kinda not surprised it's gone horribly wrong. Mirror at http://bieh.net.nyud.net/2010/11/08/xkcd-576/ http://bieh.net.nyud.net/2010/11/08/xkcd-576/
drusenko 16y ago
The Wordpress default install is horribly slow out of the box. The sad reality is that most blog software is not tuned to serve any reasonable number of pageviews by default. It's one reason why letting someone manage all that for you makes sense. (Shameless plug) At Weebly we spent a lot of time making sure that our blogging engine is very optimized. We have free users -- they don't pay us any money, we don't place any ads on their site, and they even use their own domain -- hit the front page of Digg/Reddit/HN all the time, and we can easily handle it in stride.

by vog 16y ago

steveklabnik 16y ago

Given the popularity of Wordpress on LAMP, it could be something like KeepAlive: 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...

bieh 16y ago
I tried this, the site seems much more responsive now. Thanks!
- boyter 16y ago
  I did the same thing when searchforphp hit the front page. Before I disabled it the server died under the strain. Following it everything was smooth sailing again.

bieh 16y ago

It's working again now. Although I had to lower the number of maxworkers to get it stable, so it may be slow. And yeah, I'll be investigating why it's so slow tomorrow after the heat dies down. I think this is the first time that wordpress instance has served more than a few hits per day, so I'm kinda not surprised it's gone horribly wrong. Mirror at http://bieh.net.nyud.net/2010/11/08/xkcd-576/ http://bieh.net.nyud.net/2010/11/08/xkcd-576/

drusenko 16y ago

The Wordpress default install is horribly slow out of the box. The sad reality is that most blog software is not tuned to serve any reasonable number of pageviews by default. It's one reason why letting someone manage all that for you makes sense. (Shameless plug) At Weebly we spent a lot of time making sure that our blogging engine is very optimized. We have free users -- they don't pay us any money, we don't place any ads on their site, and they even use their own domain -- hit the front page of Digg/Reddit/HN all the time, and we can easily handle it in stride.