Proposed job schedule:
TODO:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | Halfak | T112319 Revscoring integration as a beta feature | |||
| Resolved | None | T120183 Improve mwext-ORES integration with RecentChanges | |||
| Resolved | None | T120923 Ask for consensus to enable and deploy ORES extension to production | |||
| Resolved | awight | T112856 Write prototype MediaWiki extension to surface ORES scores | |||
| Declined | None | T115785 Set up periodic maintenance jobs for ORES cache |
Proposed job schedule:
- CheckModelVersions should run something like hourly. This period determines how much data will be incorrectly labelled with an older model version, and therefore be unnecessarily refreshed.
Too fast. Models get updated once in a while and in that case manual run is much more desirable.
- PurgeScoreCache can run daily.
Too fast. See above.
TODO:
- There should be a "dirty" flag set and cleared on the ores_model table dependending on whether we know there is old data in the cache.
Schema has changed and this flag is already there.
- Consider purging cached scores on revisions older than 30 days?
No, if score of an edit in a certain version changes, we would have much bigger problems. It's a big sign of "something is wrong"