Issue metadata
Sign in to add a comment
|
Ensure network service doesn't regress performance |
||||||||||||||||||||||
Issue descriptionIdeally network service improves performance, but at a bare minimum we shouldn't regress. Using Cluster Telemetry [1] to get some initial numbers on desktop [2], it looks like we're 17% slower. Hopefully there are low hanging fruit as we haven't looked into this before. [1] https://www.chromium.org/developers/cluster-telemetry [2] https://ct.skia.org/results/cluster-telemetry/tasks/chromium_perf_runs/jam-20180321232641/html/index.html ⛆ |
|
|
,
Mar 26 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16ff2143440000
,
Mar 26 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16ff2143440000
,
Mar 27 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/149da9f3440000
,
Mar 27 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12ff306b440000
,
Mar 27 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/128bda1b440000
,
Mar 27 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/149da9f3440000
,
Mar 27 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/128bda1b440000 Test: Enable NS in loading.desktop by chongz@chromium.org https://chromium-review.googlesource.com/c/chromium/src/+/981436/3 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 28 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/12ff306b440000
,
May 9 2018
,
May 18 2018
This bug will not block canary
,
May 22 2018
,
Jun 1 2018
,
Jun 1 2018
,
Jun 7 2018
,
Jul 23
,
Aug 24
,
Aug 24
,
Aug 29
,
Sep 28
,
Oct 9
,
Dec 11
,
Dec 11
,
Dec 11
|
||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jam@chromium.org
, Mar 22 2018