Thanks Ben -- that's pretty compelling. IMO the day when the general
population moves beyond pre-fork into an event-driven model cannot come soon
enough.
In fact, your observation is consistent with my experience with "httpd -X"
where the waterfall diagram in Firebug for a page refresh had approx
On Tue, Apr 12, 2011 at 02:18, Joshua Marantz wrote:
> What are the reasons someone might wish to turn KeepAlive off? The only one
> I can think of is in single-process mode (httpd -X) it can be a drag to
> refresh a page with lots of resources; but this seems like a secondary issue
> that could
webpagetest.org gives a big red *F *to web sites that do* *not have
KeepAlive enabled. Yet, at least in the CentOS installation of Apache, it
is off by default. Why is that? What are the reasons that KeepAlive should
be off?
The default in 2.2 is on for KeepAlive.
Redhat's docs (right or wro
webpagetest.org gives a big red *F *to web sites that do* *not have
KeepAlive enabled. Yet, at least in the CentOS installation of Apache, it
is off by default. Why is that? What are the reasons that KeepAlive should
be off?
Although it's trivial to turn it on in httpd.conf, many web sites do n
