| Issue 200: | Schedule replication by remote URL, not per-project | |
| Back to list |
Reported by Shawn Pearce <sop@google.com> on Wed May 27 21:41:27 PDT 2009 Source: JIRA GERRIT-200 Affected Version: 2.0.13 When replicating to more than one destination we should try to arrange the worker threads such that they operate on a per-destination basis, rather than per-project. This will prevent PushQueue from flooding one host with multiple concurrent workers pushing to different projects on the same system, while starving other hosts of getting replication service. The general idea is, we really want to isolate any given host from the others, so that really slow network doesn't starve the other, potentially faster, replication destinations.
Sep 24, 2009
#1
code-rev...@gtempaccount.com
Sep 24, 2009
Update by Shawn Pearce <sop@google.com> on Sat May 30 11:25:36 PDT 2009 Fixed in version 2.0.13.
Status:
Fixed
Sep 25, 2009
(No comment was entered for this change.)
Labels:
FixedIn-2.0.13
Oct 25, 2012
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |