After enabling xkill (T172914: [Tracking] Fine-grained change notifications based on tracking from Lua getters via __index) and T185693: Implement a (more liberal) usage aspect deduplicater (days: 3), the size of the recentchanges table and wbc_entiy_usage table is changing drastically. Optimizing them will free lots of space. The most prominent changes will happen on: cawiki, ruwiki, hywiki, commonswiki, and then with less extent: bewiki, glwiki, frwiki, eswiki, jawiki, huwiki, kowiki, svwiki, nlwiki, fawiki, ptwiki
I would recommend doing the optimization of the wbc_entity_usage at least after the next week so changes propagate through caches and actually removes the rows. And optimizing the recentchanges table at least the next month (Let's say late March) so with the one-month timespan of recentchanges it gets to its minimum size unless there is storage issue and then we can do it twice. Thank you!
wbc_entity_usage defragmenting process (recentchanges was tracked at T178290):
- bgwiki s2
- itwiki s2
- svwiki s2
- zhwiki s2
- bewiki s3
- cewiki s3
- dawiki s3
- hywiki s3
- ttwiki s3
- frwiki s6
- arwiki s7
- cawiki s7
- huwiki s7
- rowiki s7
- ukwiki s7