Issue metadata
Sign in to add a comment
|
3.8% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 594279:594310 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 1
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14d8aed8e40000
,
Oct 2
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/14d8aed8e40000 [turbofan] Remove redundant isolate argument from typers. by neis@chromium.org https://chromium.googlesource.com/v8/v8/+/74b40e34d56946e450fa96673357f5a593dc5683 23.87 → 23.46 (-0.4064) [interpreter] Separate bytecodes for one-shot property loads and stores by chandanreddy@google.com https://chromium.googlesource.com/v8/v8/+/eccf18674911a3d8a84213589e4bda70bf81aeb1 23.52 → 24.54 (+1.016) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Oct 4
,
Oct 5
Looks like One-shot CL is not the cause of regression https://pinpoint-dot-chromeperf.appspot.com/job/165ed9e4e40000
,
Oct 17
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 1