Ensure sizes test is measuring the right things on Linux |
||||
Issue descriptionWe've moved the sizes step to the main perf waterfall, so that we're certain it runs on official release builds and we can run it on every revision. Now we'd like to ensure that it is measuring the right things. Here is the code: https://code.google.com/p/chromium/codesearch#chromium/build/scripts/slave/chromium/sizes.py&q=sizes.py Here are the graphs: https://chromeperf.appspot.com/report?sid=a514f920dd8efd47095d638a55303444b0c85ad57d7b9308c58a37e4dcdf810e (Lots more things to plot if you open up the "Subtest" menu) Does this all look correct? If so, what should we monitor? It's currently set to monitor just chrome, which seems wrong. Should it be chrome-stripped? Assigning to Rachel to find someone to answer the questions. Thanks for your help!!
,
May 23 2016
Lei and Michael would probably be the right people to confirm what's being monitored is correct, but to my eyes yes those look like the right things.
,
May 23 2016
I looked at the graph again today, and the "ChromiumPerf/linux/sizes / chrome-stripped / stripped" numbers look like the ones we care about. It's approximately what we ship to users.
,
May 23 2016
Thanks! I updated monitoring to ChromiumChrome/Google Chrome Linux x64/sizes/chrome-stripped/stripped
,
May 23 2016
Issue 606294 has been merged into this issue.
,
May 23 2016
Sorry, I missed this (bad filter which is now fixed!) |
||||
►
Sign in to add a comment |
||||
Comment 1 by sullivan@chromium.org
, May 20 2016