Closed
Bug 616298
Opened 14 years ago
Closed 14 years ago
consider increasing changeCacheSize on masters
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
Details
Attachments
(1 file)
338 bytes,
patch
|
Details | Diff | Splinter Review |
We had the schedulers fall down today after quite a few pushes with 100s of changesets came in around the same time. It's possible that having a larger change cache would've helped them cope better.
Comment 1•14 years ago
|
||
The default cache size is 50. I set the tests scheduler to have a limit of 10,000. After processing the backlog of changes, there were 3,300 changes in the cache, so I think 10,000 is a good number to go with for now. I think Change objects weigh in at about 5kB each (varies with # of files, etc.), so 10,000 of these is 50 MB of memory?
Reporter | ||
Comment 2•14 years ago
|
||
This is the patch Catlee locally applied to pm02, for the tests scheduler. I'm going to land it along with some other things shortly.
Reporter | ||
Comment 3•14 years ago
|
||
Masters have been updated.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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
•