Closed
Bug 692823
Opened 13 years ago
Closed 13 years ago
Optimize timing of PGO scheduler
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: armenzg)
References
Details
(Whiteboard: [buildfaster])
Attachments
(1 file)
826 bytes,
patch
|
coop
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
Every 4 hours we trigger sets of PGO builds which create sets of test jobs.
This actually creates a lot of load on the testing side (8 sets of PGO by ~20 of suites per 4 PGO enabled testing OSes).
There are several optimizations we can do:
* only run PGO builds on m-c and m-i (bug 692812)
* reduce it to every 6 hours
* PGO build sets for each branch should not happen at the same time
* skip doing a PGO set when the nightly build happens as the nightly already is PGO
Assignee | ||
Comment 1•13 years ago
|
||
Let's reduce the set of PGOs until bug 691675 is fixed.
Do 4 PGO sets instead of 6 PGO sets a day.
This would be equivalent to have 2 pushes less a day per branch (minus OSX builds).
This would save around 640 tests a day (4 branches by 2 sets of PGO sets by ~20 suites per 4 PGO enabled testing OSes) and 24 builds a day (4 branches by 2 sets by 3 PGO enabled platforms).
Attachment #566249 -
Flags: review?(jhford)
Assignee | ||
Updated•13 years ago
|
Attachment #566249 -
Flags: review?(jhford) → review?(coop)
Updated•13 years ago
|
Attachment #566249 -
Flags: review?(coop) → review+
Assignee | ||
Comment 2•13 years ago
|
||
Comment on attachment 566249 [details] [diff] [review]
do PGO builds every 6 hours instead of 4 hours
http://hg.mozilla.org/build/buildbot-configs/rev/e0769b0a3dad
Merged and reconfigured.
Attachment #566249 -
Flags: checked-in+
Updated•13 years ago
|
Assignee: nobody → armenzg
Status: NEW → RESOLVED
Closed: 13 years ago
Priority: -- → P3
Resolution: --- → FIXED
Whiteboard: [buildfaster]
Updated•12 years ago
|
No longer blocks: pgo-improvements
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•