Issue metadata
Sign in to add a comment
|
11.3% regression in blink_perf.bindings at 611402:611760 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 10
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1262164c140000
,
Dec 10
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/1262164c140000 Add JavaScript for WritableStream serialization by ricea@chromium.org https://chromium.googlesource.com/chromium/src/+/c5d30387058ced52f3007b1430e3539d113134ce document-implementation: 2777 → 2841 (+63.9) heap: Introduce not fully constructed state for objects during ctor by mlippautz@chromium.org https://chromium.googlesource.com/chromium/src/+/e2059e53bea9548648de1ce7e06e239b89f2c580 document-implementation: 2818 → 2590 (-228.3) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/blink-perf-benchmarks |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 10