Page MenuHomePhabricator
Create Task
Maniphest T433530

Backfill Edit Suggestion Counts in Linked Artifacts Cache for technical pilot
Open, Needs TriagePublic
Actions

Description

The technical pilot of Edit Suggestion Counts stored in Linked Artifacts cache (backed by Headless VE) will only enable suggestion counts for a deterministic sample of pages.

T433024: Implement sampling requirements for Headless VE technical pilot will determine the sample proportion.

Once that is decided, we should pre-warm / backfill these suggestions for the latest revision of the pages in the sample.

Since sampling is determined in VisualEditor edit check PHP code, a PHP maintenance script that iterates through all page_ids and 'warms' the cache for pages in sample would probably suffice.

The code recently added for T432733: Server Side Edit Suggestions - Linked Artifacts Cache precompute job could be factored out into a callable function from a MW Service.

Related Objects
Search...

StatusSubtypeAssignedTask
 OpenNoneT360489 [EPIC] Offer edit suggestions as a service
 OpenNoneT416531 [EPIC] Surface Edit Suggestions outside of VE
 OpenNoneT431076 [EPIC] Surface specific edit suggestions within articles (Phase 2)
 OpenppelbergT428816 [EPIC] Surface edit suggestion counts to logged-in editors on articles (Phase 1)
 OpenppelbergT430712 [EPIC] Launch controlled experiment of surfacing suggestion counts on articles to logged-in editors
 OpenNoneT433530 Backfill Edit Suggestion Counts in Linked Artifacts Cache for technical pilot
 OpenNoneT432286 [MILESTONE] Run technical pilot to evaluate Headless VE resource requirements
 OpenEsandersT428811 [EPIC] Deploy headless VE
 OpenEsandersT428491 [EPIC] Build a headless mode for EditCheck that scrapes suggestions and outputs them via an API
 ResolvedEsandersT431326 Decide on mechanism by which we will trigger headless VE
 ResolvedEsandersT431492 Server Side Edit Suggestions - Headless VE - LAC gRPC lambda interface
 ResolvedEsandersT431495 Server Side Edit Suggestions - Headless VE - request tracing
 OpenEsandersT431541 Headless VE: Allow the user to pass in which wiki to fetch from with each request
 OpenEsandersT431547 Headless VE: Create config endpoint so check account configs can be cached
 OpenEsandersT431726 Consider performance improvements for headless VE
 DuplicateNoneT431497 Deploy Headless VE in k8s for technical pilot
 ResolvedOttomataT433514 Headless VE - Docker image pipeline
 OpenEevansT431499 Linked Artifact Cache - connect to Headless VE suggestion counts lambda
 OpenNoneT436689 Deploy headless VE to staging environment
 ResolvedSpikeEsandersT431602 [SPIKE] Identify candidate suggestions that can be extracted from VE
 OpenNoneT431603 Investigate making TextMatchEditCheck run independently of VE
 OpenNoneT432046 Propose parameters for headless VE pilot
 ResolvedRscoutT432708 Application Security Review Request : EditCheck server-side suggestions
 OpenNoneT432715 Satisfy SCROLL soft launch requirements: EditCheckHeadless
 OpenjhathawayT434109 Create Headless VE Helm chart & deployment
 ResolveddchanT434129 Create a wikitech page for EditCheckHeadless
 ResolveddchanT434134 EditCheckHeadless: Ensure maintainance contact details are correct
 OpenjhathawayT433024 Implement sampling requirements for Headless VE technical pilot

Event Timeline

Ottomata created this task.Jul 29 2026, 6:23 PM

I have never written or run a maintenance script.

Open question:

If we are running a maintenance script, does it make sense to have that script submit jobs to do this? Or should the script itself just warm the cache directly?

I think submitting jobs would be better, as the JobQueue will handle them asynchronously as quickly as it can, and hopefully throttle them where it needs to slow down?

Esanders added a comment.Jul 30 2026, 12:58 PM

I think submitting jobs would be better, as the JobQueue will handle them asynchronously as quickly as it can, and hopefully throttle them where it needs to slow down?

That seems sensible. We have written and run some maintenance scripts recently - it should be fairly straightforward (https://wikitech.wikimedia.org/wiki/Maintenance_scripts)

ppelberg edited parent tasks, added: T430712: [EPIC] Launch controlled experiment of surfacing suggestion counts on articles to logged-in editors; removed: T432286: [MILESTONE] Run technical pilot to evaluate Headless VE resource requirements.Aug 5 2026, 4:39 PM
ppelberg added a subtask: T432286: [MILESTONE] Run technical pilot to evaluate Headless VE resource requirements.
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits