Closed
Bug 721864
Opened 13 years ago
Closed 13 years ago
use increased MAX_BROKER_REFS on build/test master
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 712244
People
(Reporter: bhearsum, Unassigned)
References
Details
(Whiteboard: [buildmasters][capacity][buildbot])
We continue to hit the maximum number of builders per slave, particularly on the Linu xtest machines. We need to up the MAX_BROKER_REFS so this stops breaking things.
The tegras already use it, like this:
import twisted.spread.pb
twisted.spread.pb.MAX_BROKER_REFS = 2048
in the .tac files.
We need to test it to make sure it doesn't anything.
Comment 1•13 years ago
|
||
If we take the effort to bump this, we may want to choose something like 4096 or some other largish number that we don't foresee hitting for a long long time.
Comment 2•13 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #1)
> If we take the effort to bump this, we may want to choose something like
> 4096 or some other largish number that we don't foresee hitting for a long
> long time.
Is increasing the refs that high going to have other adverse affects?
Priority: -- → P3
Whiteboard: [buildmasters][capacity][buildbot]
Comment 3•13 years ago
|
||
The increase itself will not, but I don't know about the effects of using that many refs. Most likely you will see further inordinate memory use and slowness. I don't know if the underlying algorithms are O(N) (in which case quadrupling will only make things four times slower/bigger) or O(N^2) (which would make it sixteen times slower/bigger) or what.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•