Issue metadata
Sign in to add a comment
|
35.8% regression in blink_perf.shadow_dom at 606755:606772 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 14
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1322e780140000
,
Nov 14
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/1322e780140000 Move GetFetchClientSettingsObject() to FetchContext by hiroshige@chromium.org https://chromium.googlesource.com/chromium/src/+/cb193cc583121820faf4c42d3debb2aeb1e50754 v1-mutate-shallow-tree-then-slot-flatten: 20.05 → 20.32 (+0.2667) Add assigned_nodes_index_ map for slot's assigned child by rakina@chromium.org https://chromium.googlesource.com/chromium/src/+/eaddcb2899f1120b8a8d4d30d3c2a2911e65d049 v1-mutate-shallow-tree-then-slot-flatten: 20.41 → 27.07 (+6.659) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/blink-perf-benchmarks
,
Nov 19
This can be a perf regression.
,
Nov 20
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 14