Optimize timing of PGO scheduler

RESOLVED FIXED

Status

Release Engineering
General
P3
normal
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: armenzg, Assigned: armenzg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildfaster])

Attachments

(1 attachment)

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
Created attachment 566249 [details] [diff] [review]
do PGO builds every 6 hours instead of 4 hours

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)
Attachment #566249 - Flags: review?(jhford) → review?(coop)

Updated

7 years ago
Attachment #566249 - Flags: review?(coop) → review+
Depends on: 691675
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

7 years ago
Assignee: nobody → armenzg
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Priority: -- → P3
Resolution: --- → FIXED
Whiteboard: [buildfaster]
No longer blocks: 692699
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.