Last modified: 2014-05-18 01:46:36 UTC
Re: https://gerrit.wikimedia.org/r/109710 We should find a way to re-expose this information. The current solution sucks because many wikis are inappropriately using miser mode (given its myriad other functions) and most templates don't have many transclusions (it's a long tail). I believe we already set up caching for the info action's output. We could get more granular with the caching, if necessary.
People are asking questions about it too... https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Transclusion_count_missing_at_action.3Dinfo_pages
Seems like the cache version for info action needs to be changed to clear the old info actions from cache, with shows this number actually.
Potential work around: *estimate with EXPLAIN *if estimate < 5000 do real query (5000 pulled out of my hat) *otherwise round the estimate (since explain only rough order of magnitude, 512374 implies non existent precision), and output something like "roughly 510,000" Possibly something similar should be done for other queries which could potentially scan millions of rows in an edge case.
Can I have a timeline on this? If it's going to take a while I'll reimplement my tool (which provides just this information) in Labs. Otherwise, I shan't bother. My own personal view is that action=info could perhaps have two modes, where if the particular information you wanted wasn't available, you could request the performance intensive mode. But that's just an idea.
An alternative work around would be to use a subquery with a limit in it like mobile does
LIMIT 5000 would certainly be a useful placeholder until we work out a better fix.
