I am still new here, and my wiki is starting to have problems with the search box autocomplete slowing down. What took 1-3 sec. now takes 6 sec. to give a suggestion list of pages from the upper right search box. Could I get a top 12 list of common things to do / check when the search box autocomplete slows down? Think it would help me and others. Thank you a head of time.
Product and Version information to take into consideration:
MediaWiki 1.21.2 PHP 5.4.14 (cgi-fcgi) MySQL 5.5.25
You could try running the rebuildall.php script to rebuild the searchindex. Basically this table should be up to date, but I have seen cases, where old pages did not get removed properly leading to wrong entries in the table.
That is a good tip. I also like to use rebuildLocalisationCache.php --force as part of the maintenance I do.
1. run rebuildall.php and rebuildLocalisationCache.php --force 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12.
Any other suggestions? Anyone?
Hello!
How long takes a normal page view, until it's finished? Is it slow, too?
P.S.: You should think about to upgrade your MediaWiki version, 1.21 isn't supported anymore :)
Normal Page loads quickly. And, yes I will be upgrading at some point.
Hi please upgrade to mediawiki 1.23 and for the slow search bar it could be that the server is slow.
(Where I don't see where this might in any way help solve the actual issue.)
Hi Everyone,
I finally got some time and upgraded to 1.23, and also put in place an identical server to play with. Both servers are very close in the configuration of IIS, PHP, MediaWiki, etc. (excluding hardware) and both have about the same response time on the search.
The search is a little faster after the upgrade, but have I noticed the following. If I type in a whole word like “laborious” it takes 3 – 4 seconds, but if I just type “L” wait 2-3 seconds “L” words are listed below (as expected), and as I type the sort narrows to “laborious” quickly. If clear the search box and now type in “laborious” it is listed right away. Do not think the Hardware is the issue, lots of RAM, Processing power, Drive space with high I/O speed. Also, I get the same behavior on the twin server which has far less processing power and memory. Cache maybe? Ideas anyone?
