1.3.6 and 1.3.7 are terribly, terribly slow for me, and I don't use rewrite rules at all I spent ages putting Apache and MySQL into highperformance modes, recompiled most of the OS for Pentium III, tweaked anything I could to get a speed boost, with little effect. Went back to 1.3.5 and it was fast again, faster than before due to the tweaks. For some reason I can't think of any reason for, Mozilla looks for favicon.ico about 20 times on 1.3.7 and only about 4 times on 1.3.5. So its possible there is some rewrite-looking-for-stuff going on. Cian

I was then, I'm not now... Another issue I noticed then but haven't checked since was that when $wgWhitelistRead was on, IE users got a script error on the front page if not logged in and didn't if logged in. I don't use Windows so I haven't checked since. Err, where to start... My 1.3.5 was extensively modified, although not on any of the files 1.3.6 changed. I've got $wgWhitelistEdit (I think thats what its called) turned on, the copyright notice on the edit page hacked out, extra buttons added to the editbox, and a few other random hackjobs to make it work better in the enviroment I use it. But no major changed to config files. Cian

I actually don't know.... Network admin did set up a hostname for it (khost.finance.gov.ie), but I'm not sure it was actually propogated out to to web. I can't actually tell because I'm on the Intranet here.

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? ----- Original Message ----- From: "Cian Duffy" <myob87(a)gmail.com> To: "MediaWiki announcements and site admin list" <mediawiki-l(a)wikimedia.org> Sent: Tuesday, November 02, 2004 12:39 PM Subject: Re: [Mediawiki-l] Regarding delay

Well as in my first post with the original problem, this machine is a little slow but can definitely handle the loads. mysql is local ( very small loads) and I am not using any php acceleration modules, there has never been a need. I have not configured LocalSettings.php at all, this is a stock installation. Just was wondering if this is a common problem with stock installations of mediawiki? I certainly cannot find the problem. I have tried your suggestions yet still no (noticeable) difference. ----- Original Message ----- From: "Brion Vibber" <brion(a)pobox.com> To: "MediaWiki announcements and site admin list" <mediawiki-l(a)Wikimedia.org> Sent: Tuesday, November 02, 2004 10:24 PM Subject: Re: [Mediawiki-l] Regarding delay On Nov 2, 2004, at 6:53 PM, N. Mourtos wrote: 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)

On Nov 3, 2004, at 5:41 AM, N. Mourtos wrote: Can you be more specific as to how slow it is? From here we can't tell whether you're running a 486 or a Pentium 4. If you're on the 486 end of the scale, then I'm not too surprised that it's sluggish. :) I highly, highly, highly recommend a PHP acceleration module. Have you tried it? Which one? Can you confirm that it's enabled? (Check phpinfo() output for a section showing the module's version and settings.) Did you enable profiling to see which functions are taking up how much time? Could you post the output? -- brion vibber (brion @ pobox.com)

On Nov 3, 2004, at 1:54 PM, N. Mourtos wrote: Yeah, that's your problem. :) This was my primary suggestion, and you did say you followed my suggestions and didn't see any difference. I highly, highly recommend you do this first before trying anything else. With a current PHP this should be pretty simple; the APC cache module can be installed like this (run as root): pear install apc That will download the current APC source, compile it, and install the module into PHP's extensions directory. Then edit php.ini and add a line like: extension = /usr/lib/php/extensions/no-debug-non-zts-20020429/apc.so (this should be the actual location of the installed apc.so file.) Restart Apache. Check Apache's error_log to make sure there aren't any failure messages about shared memory allocation or inability to load the module. Create a php file like this: <?php phpinfo(); ?> and browse to it. Make sure there is a section describing the apc module. Can you list exactly what you've added to LocalSettings.php, and exactly where you've looked for the output? Did you see any error messages? -- brion vibber (brion @ pobox.com)

Is it worth setting her up if in the end she will run to slow? I really never thought that this engine could ever be so CPU intensive. ----- Original Message ----- From: "Brion Vibber" &lt;brion(a)pobox.com&gt; To: "MediaWiki announcements and site admin list" &lt;mediawiki-l(a)Wikimedia.org&gt; Sent: Wednesday, November 03, 2004 5:24 PM Subject: Re: [Mediawiki-l] Regarding delay