Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm running MediaWiki 1.23 on the following machine:

  • Windows Server 2008 R2
  • IIS 7.5
  • PHP 5.4.34
  • Separate database server with MySQL 5.6.26

I was previously running this setup on a supposedly-identical machine, but since the transition I've seen the response times of wiki pages increase over time. Rebooting the application server brings the response times back into family. Please see the chart below showing the old server in blue (stable response times), and the new server in orange with steadily increasing response times which are reset by rebooting.

the chart below

Also see the gray line which shows number of hits per day, which is relatively stable (though decreasing slightly probably due to my users not enjoying the slowness).

What could be causing this?

EDIT: The chart above has been updated with the latest data and some annotations.

share|improve this question
are you running low memory when response time increase ? did you tracked response times between Mysql server and your IIS server ? – Froggiz Nov 9 at 15:05
We're not running out of memory, and the response times for MySQL queries are not the issue. – Jamesmontalvo3 Nov 9 at 18:44
anything special in IIS log that could be different from before and after migration ? the disk on old server and new use the same technologie ? in fact you need an benchmark on old system and the new to compare, cause i ddon't which wiki config could do that (execpt bad rewriting) – Froggiz Nov 9 at 19:05
I'm unfortunately not the system administrator, so I don't have direct insight into what is different. By posting here I'm hoping to get some ideas for what to ask the system administrator to check. – Jamesmontalvo3 Nov 9 at 19:52
@Froggiz what did you mean when you said "except bad rewriting" in the comment above? – Jamesmontalvo3 14 hours ago

1 Answer 1

You can increase performance with wiki configuration:

this is an exemple with my config

# Shared memory settings
$wgMainCacheType = CACHE_ACCEL; #PHP APC
$wgMemCachedServers = array(); 

# Parser Cache
$wgParserCacheExpireTime = 604800; #1 Week

# Load.php expires
$wgResourceLoaderMaxage['versioned']['server'] = 604800;
$wgResourceLoaderMaxage['versioned']['client'] = 604800;
$wgResourceLoaderMaxage['unversioned']['server'] = 604800;
$wgResourceLoaderMaxage['unversioned']['client'] = 604800;

# Job.php rate
$wgJobRunRate = 0;

# Sidebar cache
$wgEnableSidebarCache = true;

# File cache
$wgUseFileCache = true;
$wgFileCacheDirectory  = "$IP/cache";
$wgUseGzip = true;
$wgFileCacheDepth = 0;

# Cache folder
$wgCacheDirectory = "$IP/cache";

then you can add some perf with IIS options:

  • add expire header
  • add cache control
  • add output compression

after you did some optimization, you can test it trought google page speed insight :

share|improve this answer
These are all good suggestions, but as I said I was on an identical server before and did not have these issues. Well, supposedly it was identical, but clearly something is different. – Jamesmontalvo3 Nov 9 at 18:47
i know but at least some infos are there if someone else make a search on wiki perf trouble – Froggiz Nov 9 at 19:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.