New issue
Advanced search Search tips

Issue 895379 link

Starred by 1 user
Status: Fixed
Owner:
ethannicholas@google.com
Closed: Dec 17
Cc:
npm@chromium.org
ethannicholas@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.4%-42.7% regression in rendering.mobile/tasks_per_frame_total_all at 599374:599451

Project Member Reported by npm@chromium.org, Oct 15 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 15 

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 22

Cc: ethannicholas@google.com
Owner: ethannicholas@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1210fd9ce40000

converted AARectEffect to new FP system by ethannicholas@google.com
https://skia.googlesource.com/skia/+/222e275b0ab4c8a2af152c637bf9dbc28b4a097f
thread_raster_cpu_time_per_frame: 0.969 → 1.354 (+0.3849)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by ethannicholas@google.com, Dec 17

Status: Fixed (was: Assigned)
This was reverted.
►

Sign in to add a comment