Configure maximum_workers based on Branch type

Bug #153779 reported by Jonathan Lange
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Low
Unassigned

Bug Description

Bug 153778 might make this less useful, but it's still worth tracking.

Currently the puller runs a number of subprocesses less than or equal to the maximum_workers configuration variable. This variable is the same across branch types, even though different branch types have differing performance requirements.

Jonathan Lange (jml)
Changed in launchpad-bazaar:
importance: Undecided → Medium
status: New → Confirmed
Jonathan Lange (jml)
Changed in launchpad-bazaar:
assignee: nobody → jml
milestone: none → 1.1.11
Jonathan Lange (jml)
Changed in launchpad-bazaar:
milestone: 1.1.11 → none
Revision history for this message
Jonathan Lange (jml) wrote :

Unassigning.

Changed in launchpad-bazaar:
assignee: jml → nobody
importance: Medium → Low
status: Confirmed → Triaged
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

We've mutilated the system to the point where this doesn't really matter any more, I think.

Changed in launchpad-code:
status: Triaged → Invalid
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.