[17:05:01] I host the website/forum/wiki of a community, and having some issues where mediawiki pages will either never load (as if stuck in a loop) or take ages, and once finally loaded is shown in a raw output. This has caused apache to drain all the CPU cores.. It seems to be related to history view, when comparing a very recent version to a really old one like this: http://www.adventuregamestudio.co.uk/w/index.php?title=Hall_of_Fame [17:05:01] &diff=10684&oldid=6452 [17:05:24] Anyone got any idea what could be causing this, and what I could do to sort it out? [17:07:31] Presumably because it's a big diff... [17:08:17] I just made php log all errors etc.. and it throws this error: "Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/ags/w/includes/diff/DairikiDiff.php(453) : assert code on line 0" it seems to start using longer times at TableDiffFormatter->changed() in DiffFormatter.php [17:08:26] (once the page finally do load) [17:08:56] Makes sense [17:08:58] you can do something like (1) in your Localsettings.php temporarily, until you fix this [17:09:02] (1) ini_set('max_execution_time', 30000); [17:09:05] If the file is a lot different.... [17:09:48] If you're feeling overly adventureous you could switch from using PHP to HHVM [17:14:05] hmm [17:19:03] Certainly increase the timeout for now, see how it looks [17:25:12] that doesn't seem right. If the diff is draining all CPU cores, increasing the timeout would make things worse... unless the diff is finally resolved and cached [17:25:53] impacient users will stomp F5 anyway if it takes more than 30 seconds [17:30:24] is diff multi cored? :D [17:30:33] (php certainly isn't) [17:33:24] no, but an impacient user hitting F5 multiple times makes it multi core :D [17:47:30] I've had several occations where my CPU is fully drained because of these requests [17:47:46] and at some points they seem to "hang"