New issue
Advanced search Search tips

Issue 875361 link

Starred by 1 user
Status: Fixed
Owner:
r...@chromium.org
Closed: Aug 18
Cc:
tdres...@chromium.org
r...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.6%-18.5% regression in tasks_per_frame_total_all,thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 582015:582034

Project Member Reported by 42576172...@developer.gserviceaccount.com, Aug 17 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 17 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=875361

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=fbc65206253933a12739bdadbad87961828a6a5981133a4352d4ad9c9db86dd6


Bot(s) for this bug's original alert(s):

Android Nexus5X WebView Perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 18

Cc: r...@chromium.org
Owner: r...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15c0f214640000

Revert "Roll clang 337439:338452." by rnk@chromium.org
https://chromium.googlesource.com/chromium/src/+/8457b638ed3550460518321e4a4a21b08c2e30f9
0.7512 → 0.8622 (+0.111)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by r...@chromium.org, Aug 18

Status: Fixed (was: Assigned)
This was a compiler update revert that relanded in https://chromium-review.googlesource.com/c/chromium/src/+/1174546, and the regression should be fixed.

Presumably the compiler update improved the benchmark, the revert regressed it, and the re-land should've improved it again.
►

Sign in to add a comment