Here's three things I wish I had read about Apache optimization that are not
commonly discussed (we found out by years of trial and error). These three
settings are worth more than all the other optimization we've done (e.g.
SendBufferSize, AcceptFilter http data, EnableMMAP On, EnableSendfile
if your server averages 300 simulatious connections, you need
to start with 300 servers, and you never want it to drop
below that number.
Your experience might show otherwise however based on our experience - if we
averaged 300 new customers/min at once (not 300 requests/sec) a
MinSpareServers
On 3/22/2010 5:08 AM, Geoff Millikan wrote:
if your server averages 300 simulatious connections, you need
to start with 300 servers, and you never want it to drop
below that number.
Your experience might show otherwise however based on our experience - if we
averaged 300 new customers/min
On 22 Mar 2010, at 08:34, Geoff Millikan wrote:
Here's three things I wish I had read about Apache optimization that are not
commonly discussed (we found out by years of trial and error).
Thanks for sharing!
1. Set your KeepAliveTimeout to 3 seconds or less.
+1. Isn't that documented?
Fair enough, but if your testing was of ~30 requests, and we
are believing that
the typical browser is making 6 simultaneous connections,
then it sounds like
the real magic was 6 * fudge factor of 5 ;-P
LOL, yes, I totally agree and I kept thinking that no optimization guide has
On Mon, Mar 22, 2010 at 3:45 PM, Geoff Millikan gmilli...@t1shopper.com wrote:
Fair enough, but if your testing was of ~30 requests, and we
are believing that
the typical browser is making 6 simultaneous connections,
then it sounds like
the real magic was 6 * fudge factor of 5 ;-P
LOL, yes,
+1. Isn't that documented? I'm surprised!
Suppose so, as a n00b though, I thought maybe cutting the default time of 15
in half would do it. It didn't. With many people on fast Internet
connections now, even 1 or 2 second KeepAliveTimeout's seem to work good.
Interesting! Do you have any
