New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 905193 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

933.6% regression in rendering.mobile/queueing_durations at 607128:607158

Project Member Reported by chiniforooshan@chromium.org, Nov 14

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=905193

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


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

Android Nexus5X WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
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/17b712dfe40000

mojo: Use a more appripriate task runner at HandleSignalTracker's SimpleWatch by hajimehoshi@chromium.org
https://chromium.googlesource.com/chromium/src/+/cb5a960bf9cf62fc934f8a167ac4da6219080aa2
queueing_durations: 0.2714 → 2.706 (+2.434)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: altimin@chromium.org roc...@chromium.org
Not sure how to interpret this?
Status: WontFix (was: Assigned)
I think this is because used task runners are just changed.
+1 to won't fix. Doesn't seem to be a real regression.

Sign in to add a comment