Fine-tune Linux/Win "sizes" metrics to produce fewer alerts? |
||
Issue descriptionIt seems the tests are creating alerts even for very small (< ~0.1%) changes. Here is an example: https://chromeperf.appspot.com/group_report?sid=59f91245344e8d90e3508368ba8add46213482276a9db8d2becce3d6f2e4c492 Regression sheriffs have to ignore them anyway, so I think it would be better if we can skip alerts for changes below a reasonable threshold (absolute/percentage). thestig@: Do you agree as the test owner?
,
Dec 19
We probably need to first clean up our measurements and make sure we are measuring the relevant / correct sizes. On Linux, the chrome sizes are approximately 5.5 GB. I'm guessing this is an unstripped file size. But we don't really care about that. What we care about is the stripped chrome binary size, and the size of the .deb / .rpm we ship to users. On Windows, why do we even bother measuring sizes of .pdb files?
,
Jan 7
Today I encountered these ~25 alerts appearing on the dashboard for Windows .pdb files, none of them should need manual triage IMO: https://chromeperf.appspot.com/group_report?sid=7c5d266d506e60dcf164e2f0c96d4c97b625097f867cde6d9804bb6e7fe3f084 |
||
►
Sign in to add a comment |
||
Comment 1 by mustaq@chromium.org
, Dec 19Summary: Fine-tune Linux/Win "sizes" metrics to produce fewer alerts? (was: Is it possible to fine-tune Google Chrome Linux x64 "sizes" metrics to produce fewer alerts?)