Issue metadata
Sign in to add a comment
|
37%-50.1% regression in v8.browsing_desktop at 608701:608743 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 23
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13a1e813e40000
,
Nov 23
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/13a1e813e40000
,
Nov 26
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/133c458fe40000
,
Nov 27
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/133c458fe40000 Perfetto: Add an upper bound to number of events per proto message by oysteine@google.com https://chromium.googlesource.com/chromium/src/+/044129ce84b4e0ea59aaab9398fc9c76b51ae8d2 v8-gc-total: 225.2 → 314.8 (+89.69) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None
,
Nov 27
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 23