Issue metadata
Sign in to add a comment
|
12.7%-75.7% regression in v8.browsing_desktop at 608126:608167 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 16
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/112721b0140000
,
Nov 16
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/112721b0140000
,
Nov 21
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1615f34be40000
,
Nov 21
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/111409d3e40000
,
Nov 21
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/1615f34be40000
,
Nov 21
,
Nov 21
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/111409d3e40000 Add a testing configuration for HTMLParsingYieldTime study. by fergal@chromium.org https://chromium.googlesource.com/chromium/src/+/e2fadf24cd0c2c40009b1eb60e38f5ff3e3c859e memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size: 1.038e+08 → 1.214e+08 (+1.763e+07) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 16