New issue
Advanced search Search tips

Issue 913504 link

Starred by 2 users
Status: WontFix
Owner:
hajimehoshi@chromium.org
Closed: Dec 18
Cc:
npm@chromium.org
hajimehoshi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.5%-15.2% regression in rendering.mobile/tasks_per_frame_total_all at 606081:607616

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 10 

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

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


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

android-nexus5x-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 10

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

mojo: Use a more appripriate task runner at HandleSignalTracker's SimpleWatch by hajimehoshi@chromium.org
https://chromium.googlesource.com/chromium/src/+/cb5a960bf9cf62fc934f8a167ac4da6219080aa2
tasks_per_frame_total_all: 68.99 → 75.96 (+6.969)

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

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

Comment 4 by hajimehoshi@google.com, Dec 18

Status: WontFix (was: Assigned)
I think this is because used task runners are just changed.
►

Sign in to add a comment