There's gotta be a book out there about this stuff that's pretty comprehensive. Any suggestions?<br><br><div class="gmail_quote">On Tue, Jun 28, 2011 at 1:24 PM, Matthew Nuzum <span dir="ltr"><<a href="mailto:newz@bearfruit.org">newz@bearfruit.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br><div class="gmail_quote"><div class="im">On Tue, Jun 28, 2011 at 12:06 PM, Kenneth Younger <span dir="ltr"><<a href="mailto:kenny@sheerfocus.com" target="_blank">kenny@sheerfocus.com</a>></span> wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm not sure what exactly occurred. It's a basic LAMP server with an nginx proxy doing some caching there.<br><br>Running this server has been humbling, because I used to think I knew what I was doing with regard to running a server - but this thing has given me a new respect for the subtle configuring that an expert can make.<br>
<br>I know this isn't HUGE traffic, but it was getting 3000-4000 pageviews an hour at peak, which is the most traffic I've ever seen on a site I run. I think my problem is I just don't know how to tell what went wrong after the fact...<br>
<br>How would tell if it ran out of memory, or the CPU was just fully pegged, or the disk started thrashing?<br><br>-Kenny<div><div></div><div><br></div></div></blockquote><div><br></div></div><div>I know the feeling.</div>
<div><br></div><div>PHP can be a bit harder to tune because the interpreter is part of Apache. Therefore it's hard to estimate how many child processes your system can support. If I was on a 512MB system I'd probably limit it to 20 and double that for a 1G or bigger system. If you find you've got a lot of spare memory under load then you can decide where to put it, often MySQL is a good candidate. </div>
<div><br></div><div>I've seen situations like yours happen a few times in the last 18 months. In each case it was out of file handles. If that happens you're toast. You can't log in remotely to do anything about it.</div>
<div><br></div><div>What I've done, and has paid off in spades, is run Xen to create my own VPS on a dedicated server. It means you need an extra IP address but it also means you've got a guaranteed bit of a safety net. You can ssh into your xen host (aka dom0) and then take over the console of your vm that's gone out of control and try to fix it or at least hold its hand in its final hour. It also means that a physical server can be divided up into smaller servers which might be convenient. LXC may be a good alternative if you aren't able to run Xen.</div>
<div><br></div></div><div><div></div><div class="h5"><br>-- <br>Matthew Nuzum<br>newz2000 on freenode, skype, linkedin and twitter<br><br><p>"Opportunity is missed by most people because it is dressed in overalls and looks like work." -Thomas Edison</p>
<br>
</div></div><br>_______________________________________________<br>
Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><font color="#888888">Kenneth Younger III<br>Founder, Sheer Focus Inc.<br>e: <a href="mailto:kenny@sheerfocus.com" target="_blank">kenny@sheerfocus.com</a><br>p: (515) 367-0001<br>
t: <a href="http://twitter.com/kenny" target="_blank">@kenny</a></font><br>