Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Get MediaWiki
Get extensions
Tech blog
Contribute
Support
User help
FAQ
Technical manual
Support desk
Communication
Development
Developer portal
Code statistics
mediawiki.org
Community portal
Recent changes
Translate content
Random page
Village pump
Sandbox
In other languages
Add links
Search
Search
English
Appearance
Donate
Create account
Log in
Personal tools
Donate
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
ORES/Multiscore problem
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Cite this page
Get shortened URL
Download QR code
Print/export
Create a book
Download as PDF
Printable version
In other projects
Appearance
move to sidebar
hide
From mediawiki.org
<
ORES
Warning:
The ORES infrastructure is being deprecated by the Machine Learning team, please check
wikitech:ORES
for more info.
This page describes a problem we have in celery around dependent sub-tasks.
ORES multiscore pattern breakdown.
ORES scoring activity broken down into 4 diagrams: (A) A simple request for a single score without worrying about celery can be split into IO and CPU work. (B) Requesting multiple scores for a single revision adds a minimal amount of IO and CPU. (C) This is decomposed by celery into two types of job -- one job for doing the real work and N jobs for return the result. (D) This decomposition lets parallel request de-duplicate requests for the same score. This is a common pattern.
Category
:
ORES