On 13/10/12 00:22, David Gerard wrote:
(I have just accepted root on
rationalwiki.org and am
looking around
in slight horror. I will be sending a few messages like this.)
Apache comes with KeepAlive on by default. I am unconvinced this is
actually a good idea. I just switched it off and it appears to have no
ill effects, and the server has 400MB more free memory. (Ubuntu 10.04
Linode with 4GB RAM. Six wikis, Lucene search being really fat.)
The only mention I can see on
mediawiki.org is in
http://www.mediawiki.org/wiki/Manual:Newcomers_guide_to_installing_on_Windo…
, where it's one of the defaults they say nothing about.
Apache connections are really pretty damn cheap these days. Is
KeepAlive actually a good or bad thing for MediaWiki?
- d.
Opening connections is expensive when compared to keep-alive.
You need to open a new tcp connection (several roundtrips) for each
resource (images, css, scripts). You will see the most noticeable
difference with a clean cache.
The apache docs say:
In some cases this has been shown to result in an
almost 50% speedup
in latency times for HTML documents with many images.
--
http://httpd.apache.org/docs/2.4/mod/core.html#KeepAlive
I'd keep it on, but with a small KeepAliveTimeout