Last modified: 2011-04-14 15:12:50 UTC
$wgMaximumMovedPages has a current default limit of 100. On translatewiki.net we use ini_set( 'memory_limit', '130M' );. Whenever we try to move a lot of subpages in the MediaWiki namespace (130+) the request fails on "PHP Fatal error: Allowed memory size of 136314880 bytes exhausted (tried to allocate 280258 bytes)" or something similar. Subpage moving should be made less memory intensive somehow.
Maybe have it break up the move process so that it does a few at a time in batches, that should make it less memory intense, but i don't know how hard that would be.
Job queue sounds like a match
(In reply to comment #2) > Job queue sounds like a match > I don't think that's a good idea. The limit of 100 subpages was added so that moving a bunch of subpages could reasonably be done in one request, with immediate feedback (success/error). If subpage moves are done through the job queue, there's no way to inform the user when one of the moves fails (e.g. because the target page already exists or is protected).
