4 ms·
This advice may or may not be helpful, but I have survived plenty of traffic spikes from HN etc on low RAM machines by turning Keepalive Off in the apache confi
by jazzychad 15y ago
This advice may or may not be helpful, but I have survived plenty of traffic spikes from HN etc on low RAM machines by turning Keepalive Off in the apache config file. It is on by default with a long timeout, which will tie up all the resources during heavy traffic. Lots of people don't even know about it, so hopefully this will be helpful. (this assumes, of course, you are using apache, but other http servers have similar settings)
- jmtame 15y agoi changed it to that, although my apache log files aren't really giving me anything helpful. where are the cloudkick guys when you need them? ;)
- carbocation 15y agoDo you use munin or similar monitoring tools? Jazzychad's suggestion will only help you if your apache server is fully saturated, so these monitoring tools would instantly confirm or refute the notion. I completely agree that jazzychad's suspicions are correct, by the way.
- jmtame 15y agono, but i'm going to set that up. thank you. i also realized linode is nothing like the way heroku works--that resize costed me $140. definitely not a cost-effective way to deal with traffic. i'll see if i can get it pro-rated with them since i'm only doing it for one day, and then i'll setup wpcache.
- jsprinkles 15y agoIt is pro-rated. When you resize back a credit for the unused time will be credited. You paid for May is why it cost so much.