Last modified: 2014-11-06 00:30:42 UTC
Lines 1941-1943 of CommonSettings.php: > // extra throttling until the image scalers are more robust > GWToolset\Config::$mediafile_job_throttle_default = 5; // 5 files per batch > $wgJobBackoffThrottling['gwtoolsetUploadMetadataJob'] = 5 / 3600; // 5 batches per hour Lines 2390-2396 of CommonSettings.php: > # Similar to above but not for single template/file changes > $wgJobBackoffThrottling = array( > # Avoid excessive CPU due to cache misses from rapid invalidations > 'htmlCacheUpdate' => 20, // pages/sec per runner > # Avoid excessive DB usage for backlink tables > 'refreshLinks' => 20, // pages/sec per runner > ); The later assignment to $wgJobBackoffThrottling would prevent the assignment to $wgJobBackoffThrottling['gwtoolsetUploadMetadataJob'] from having any effect. Either the earlier assignment is not needed and should be removed, or it is needed and the later assignment should be to individual keys and not the entire array. Which is the case?
I think we can get rid of the GWToolset throttling. It was mostly there to prevent the "fifty large TIFFs get thumbnailed at the same time when someone looks at Special:NewFiles" scenario, and since then thumbnail pre-rendering has been enabled (or will be real soon), so GWToolset should not contribute to that problem significantly.
This was fixed a while back.