Change Details

While investigating a page I noticed that there were requests being made to for various pages of action=history&limit=2000. MediaWiki gives users the choice of `[ 20, 50, 100, 250, 500 ]` but caps the max at 5000. Some/many (didn't count) of the limit=2000 requests just timed out because of the 60s wall clock limit. It would probably be better to cap the limit at 500 or 1000 rather than trigger these long-running queries that don't finish in time anyways.

While investigating a page I noticed that there were requests being made to for various pages of action=history&limit=2000. MediaWiki gives users the choice of `[ 20, 50, 100, 250, 500 ]` but caps the max at 5000. This matches up with https://tendril.wikimedia.org/report/slow_queries?host=%5Edb&user=wikiuser showing the slowest query as `/* IndexPager::buildQueryInfo (history page unfiltered) */` with limit 2001. Some/many (didn't count) of the limit=2000 requests just timed out because of the 60s wall clock limit. It would probably be better to cap the limit at 500 or 1000 rather than trigger these long-running queries that don't finish in time anyways.

While investigating a page I noticed that there were requests being made to for various pages of action=history&limit=2000. MediaWiki gives users the choice of `[ 20, 50, 100, 250, 500 ]` but caps the max at 5000. This matches up with https://tendril.wikimedia.org/report/slow_queries?host=%5Edb&user=wikiuser showing the slowest query as `/* IndexPager::buildQueryInfo (history page unfiltered) */` with limit 2001. Some/many (didn't count) of the limit=2000 requests just timed out because of the 60s wall clock limit. It would probably be better to cap the limit at 500 or 1000 rather than trigger these long-running queries that don't finish in time anyways.