Page MenuHomePhabricator

Create consolidated monitoring to watch for versioned_maps impact
Closed, ResolvedPublic2 Estimated Story Points

Description

Healthy: no impact on load
Unhealthy: decrease in RevisionOutputCache cache hit rate; increase in parser load; any stable cache miss

We'll want to watch the stable cache long-term.

Event Timeline

awight removed awight as the assignee of this task.May 2 2022, 1:41 PM
awight moved this task from Doing to Tech Review on the WMDE-TechWish-Sprint-2022-04-27 board.
awight set the point value for this task to 2.

We're discussing whether to stop logging the "Stable cache miss", as it turns out we missed a major use case which made the message much noiser than expected. When the stable revision and the latest revision have the same wikitext content and none of the templates have changed (for example, a vandalism change is rolled back and both revisions are still pending), then FlaggedRevs will take advantage of the main ParserCache and does not leave an additional copy of the data in the stable-version parser cache.

The data collected so far is interesting, however. It shows how often this use case happens—and my guess is that it also confirms that there are no major leaks where we're not taking advantage of the stable cache when we should. Here are the numbers:

Wikilog count
ukwiki216708
ruwiki89469
eowiki45052
fiwiki34928
arwiki11588
vecwiki4576
trwiki3446
bewiki3305
mkwiki495
idwiki236
cewiki8
kawiki6
enwiki1
enwikinews1
fawiki1