Even with a check profiling still caused me performance problems for some
reason, even for a bit after commenting it all out and restarting Apache.
Kinda scary. For now I've fallen back to generating a daily list of the
URLs with the highest response times (per the %D LogFormat option) to
hopefully narrow down the problematic (type of?) pages.
On Thu, Nov 19, 2015 at 12:49 PM, Bartosz Dziewoński <matma.rex(a)gmail.com>
wrote:
On 2015-11-19 19:11, Dave Humphrey wrote:
Don't enable debug/profiling on a server that
gets public hits, at least
in
general. Profiling slows down the page load and if you're already
borderline it will make a bad situation worse. That and you'll generate so
much profiling output it will be hard to go through and make anything
meaningful from it.
Put it on a unused server or copy the wiki installation to a new folder
and
do it from there. Then you can control the page loads being profiled.
You could also only trigger it in production by some special URL
parameter. (And get rid of it after you debug the problem, so that people
don't DOS your wiki by forcing it to profile things.)
In LocalSettings:
if ( isset( $_GET['secretprofileparameter'] ) ) {
$wgProfiler = ...
}
Then visit
https://yourwiki.example/.../?secretprofileparameter=1
--
Bartosz Dziewoński
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l