* try disabling all extensions just to elliminate faulty extension as a cause.

* enable profiling (if possible. Probably requires installing xhprof) to determine what mediawiki is spending all its time doing. This would be the most useful thing to figure out what is going on.

* if using sqlite, switch to mariadb (sqlite has poor concurrency)

Some general performance tips: * ensure that caching is enabled. On IIS you probably want to set up XCache. Otherwise use apcu. Once apcu or xcache is set up, make sure wgMainCacheType = CACHE_ACCEL;

*although windows is supported, mediawiki is definitely better tested on linux.

One Thing you havent provided is the web server being used? is it IIS? Yes, it's IIS. Thanks for the tips, Brian. I'll look into those. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.berlin(a)wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84 On 7 March 2018 at 20:59, Brian Wolff &lt;bawolff(a)gmail.com&gt; wrote: > Ok, so its hard to say just from this. Some general things that may or may > not apply: > * try disabling all extensions just to elliminate faulty extension as a > cause. > * enable profiling (if possible. Probably requires installing xhprof) to > determine what mediawiki is spending all its time doing. This would be the > most useful thing to figure out what is going on. > * if using sqlite, switch to mariadb (sqlite has poor concurrency) > Some general performance tips: > * ensure that caching is enabled. On IIS you probably want to set up > XCache. Otherwise use apcu. Once apcu or xcache is set up, make sure > wgMainCacheType = CACHE_ACCEL; > *although windows is supported, mediawiki is definitely better tested on > linux. > -- > Brian > On Wednesday, March 7, 2018, Sebastian Berlin < > sebastian.berlin(a)wikimedia.se> wrote: > > We're having issues with a MW installation that gets very slow when > > multiple users are logged in simultaneously. After a while the wiki > becomes > > unresponsive and in some cases gives HTTP error 500. This has occurred > with > > as few as three users logged in at once. > > > The wiki was installed on a Windows server 2016-server, following this > > guide: > > https://www.mediawiki.org/wiki/Manual:Installing_MediaWiki_ > on_Windows_Server_2016 > . > > My first thought was that there was too little server resources, but > when > I > > looked at the task manager, CPU was fairly consistently between 5 and > 25% > > (there were a few spikes) and the RAM was steady at around 50%. MW > version > > is 1.30.0. > > > I have turned on logging (following these instructions: > > https://www.mediawiki.org/wiki/Manual:How_to_debug#Logging), but I > can't > > find any obvious cause for this behaviour. I have compiled a list of > > messages that looks suspicious here: > https://phabricator.wikimedia.org/P6814. > > I didn't want to post the whole log since the logging instructions had > > security warnings about this. > > > Any help with how to proceed finding the cause for this and fixing it > would > > be much appreciated. > > > All the best, > > > *Sebastian Berlin* > > Utvecklare/*Developer* > > Wikimedia Sverige (WMSE) > > > E-post/*E-Mail*: sebastian.berlin(a)wikimedia.se > > Telefon/*Phone*: (+46) 0707 - 92 03 84 > > _______________________________________________ > > MediaWiki-l mailing list > > To unsubscribe, go to: > > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l > > _______________________________________________ > MediaWiki-l mailing list > To unsubscribe, go to: > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l