On Nov 2, 2004, at 6:53 PM, N. Mourtos wrote:
I just installed mediawiki 1.3.5 and I am having
the same time
delayed problems as version 1.3.7. I am not exactly sure what my
problem is. The site that it is installed on currently is
www.nerdinside.net/mediawiki-1.3.5/ . I really don't know where to
start looking for my problems. Any suggestions?
There is not any recursive redirection on your server (the typical
complaint regarding 1.3.7); simply your wiki is taking an uncomfortably
long time to return a response -- about 9-10 seconds. Static files and
declarative PHP script loads are relatively quick (under a second,
anyway), so it's probably not Apache to blame.
The first thing I need to ask: is this server simply a slow machine, or
perhaps highly loaded?
Second: are you using a PHP acceleration cache module (such as Turck
MMCache, Zend Optimizer, PHPA, or APC)? If not, you should -- a
significant portion of execution time is typically spent parsing the
PHP scripts on a vanilla PHP installation. (We use Turck on Wikipedia.)
Third: is the database server local or remote? Is it highly loaded?
Slow round-trip times to an external server could slow things down a
lot.
Fourth: Have you customized LocalSettings.php in any way? Some things
like enabling memcached support without a working memcached server can
turn your wiki into a tarpit instantly.
Fifth: try adding this line to LocalSettings.php:
$wgUseDatabaseMessages = false;
Normally it will not make much impact, but if there's something wrong
it's conceivable that the wiki might be trying to re-cache the user
interface messages from the database server on every hit. If it doesn't
seem to make a difference, leave it at true -- it's easier to customize
your wiki that way.
Finally: if nothing obvious stands out above, turn on the internal
profiling:
$wgDebugLog = "/tmp/some-file-name";
$wgProfiling = true;
Load some pages and look at the output report to see if there's a
localized hotspot. (Times reported are milliseconds total spent in that
function/section and average per-call during the request. Some sections
will be bloated by time for including of PHP code or output buffer
flush delays. Function times include functions called from that
function.)
-- brion vibber (brion @
pobox.com)