commit | e3c8d4c29cfee7c9f39c31b0584b7dd2ff2df6e1 | [log] [tgz] |
---|---|---|
author | Caleb Rouleau <crouleau@chromium.org> | Fri Dec 06 15:57:46 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Dec 06 15:57:46 2019 |
tree | e9db9a6a23042c3df782bb3eafda5b8b07d1e061 | |
parent | 10620d4bc8f1b11bbf690a8a7836f9f7e20d97da [diff] |
[Benchmarking] Abridge nexus5x system_health.memory in place. Note that this will cause some of the stories of the system_health.memory_mobile benchmark to stop being run on nexus5x bot. It will also move some stories from one physical machine to another of the same model. Since the silicon lottery principle means that devices of the same model sometimes have different performance characteristics this may cause false positive improvements or regressions do not revert this change if those regressions happen. Note even though bot_platforms.py can do automatic resharding, I decided to do the resharding manually to avoid shuffling unrelated benchmarks and because it seems that the sharding system is for some reason expecting system_health.memory_mobile to run faster than it already does (which is likely because that benchmark has a rather long metrics calculation phase, which I suspect is not covered in the timing data.) I ran ./run_benchmark list system_health.memory_mobile --browser=android --json=~/listed.json to figure out that there are 28 stories in system_health.memory_mobile with the health check tag, so that's how I know how to manually reshard. Bug: 1030788 Change-Id: I0735adc781c860a1dbbbbc3608e740e34f5f48ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1954354 Reviewed-by: Juan Antonio Navarro PĂ©rez <perezju@chromium.org> Commit-Queue: Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#722485}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .