Issue metadata
Sign in to add a comment
|
14.8% regression in blink_perf.bindings at 554130:554292 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 1 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14a1f0a3c40000
,
May 2 2018
📍 Found significant differences after each of 3 commits. https://pinpoint-dot-chromeperf.appspot.com/job/14a1f0a3c40000 Reland "[builtins] Introduce further constant & external reference indirections" by jgruber@chromium.org https://chromium.googlesource.com/v8/v8/+/3f99a376ddfc1a724f94d55b4a39986e56cd33b2 Migrate BrandcodeConfigFetcher to SimpleURLLoader by pilgrim@chromium.org https://chromium.googlesource.com/chromium/src/+/276d13940ba27627e1cc4c553f5132b03ceddb3f Revert "Migrate BrandcodeConfigFetcher to SimpleURLLoader" by rockot@chromium.org https://chromium.googlesource.com/chromium/src/+/7d0a5ff689f3970032b7d72329d3f9bf998e77c3 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
May 2 2018
,
May 3 2018
Can you investigate whether this is relevant to your change jgruber@? I'm ruling out mine (and pilgrim@'s) since combined they're obviously a net zero change.
,
May 3 2018
Interesting.. In general my CL does introduce performance regressions, see https://crbug.com/838041. I'm currently working on fixing those, but it'll take me a week or two to land the follow-up CLs. In this particular case, I'm curious why graphs seem to improve almost back to baseline at Point ID: 555349. Possibly an independent improvement? Or perhaps something else is going on?
,
May 3 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 1 2018