Implement smarter build merges for perf tests |
||
Issue descriptionThe V8 team has been doing some custom merge-builds code that will make it only merge builds if there are many builds. The motivation is that for perf bots, you want to essentially build 1 revision per build, but that comes with a risk of getting ever-growing queues if commit frequency > build cycle times. Having an algorithm that runs 1 or 2 builds most of the time and only merge builds if there are a larger number (like >2 or a higher number) should make perf sheriffing alerts easier. Relevant CL: https://codereview.chromium.org/2415703004 We should only do this for the perf bots initially, since for the other bots I think a shorter build-feedback loop is more important.
,
Jan 10
The following revision refers to this bug: https://webrtc.googlesource.com/src.git/+/a396ec6668959d65d75c3636da76c9c5dcb30c97 commit a396ec6668959d65d75c3636da76c9c5dcb30c97 Author: Oleh Prypin <oprypin@webrtc.org> Date: Thu Jan 10 12:35:12 2019 Configure logarithmic build batching for performance testers Bug: chromium:706812 Change-Id: I40b51f7123a40b52f643e6058129d1f2cd9b947f Reviewed-on: https://webrtc-review.googlesource.com/c/116065 Reviewed-by: Artem Titarenko <artit@webrtc.org> Commit-Queue: Oleh Prypin <oprypin@webrtc.org> [modify] https://crrev.com/a396ec6668959d65d75c3636da76c9c5dcb30c97/luci-scheduler.cfg |
||
►
Sign in to add a comment |
||
Comment 1 by phoglund@chromium.org
, Jan 19 2018