New issue
Advanced search Search tips

Issue 889050 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

2.1%-13.4% regression in rendering.mobile/avg_surface_fps at 592497:592590

Project Member Reported by lanwei@chromium.org, Sep 25

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/10b05e57640000
Kicking off a bisect on a wider range.
Cc: chiniforooshan@chromium.org
Owner: chiniforooshan@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/102ee3d0e40000

Telemetry: fix a SF stats collector bug by chiniforooshan@chromium.org
https://chromium.googlesource.com/catapult/+/5f6da8a57db16291c01a894083137c294b3b4e5f
19.72 → No values

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/13de34c6e40000

Buildbucket says the build completed successfully, but Pinpoint can't find the isolate hash.
All regressions except thread_raster_cpu_time_per_frame are fixed. I started another pinpoint job for thread_raster_cpu_time_per_frame.
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16904882e40000
Status: WontFix (was: Assigned)
Since pinpoint couldn't reproduce the regression, and also I noticed that the graph has a land-revert pattern (around 581613-581665 for land and 592535-592590 for revert, I'll mark as won't fix.

Sign in to add a comment