PCJ runner has no prioritisation facilities
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Colin Watson |
Bug Description
We'd like to open up asynchronous copies in Archive:
I don't think the flow rate of routine copy jobs is sufficient to justify any work on prioritising between those, but Ubuntu auto-syncs are not routine: the first one of a cycle usually involves the submission of a couple of thousand PCJs in a matter of minutes (not quite instant because Archive.
Auto-syncs are one of the very few users of Archive.
Related branches
- Aaron Bentley (community): Approve
-
Diff: 84 lines (+46/-7)2 files modifiedlib/lp/soyuz/model/packagecopyjob.py (+19/-7)
lib/lp/soyuz/tests/test_packagecopyjob.py (+27/-0)
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: packages soyuz-build |
tags: |
added: package-copies soyuz-core removed: soyuz-build |
Changed in launchpad: | |
assignee: | nobody → Colin Watson (cjwatson) |
status: | Triaged → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
It's hard to get accurate data automatically since there's nothing persistent that delimits one Archive. copyPackage( s) call from another, but from inspection of the date_created fields of early SPPHs in quantal, I believe that the first auto-sync pass contained on the general order of 3000 copies and took 1h21m.