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

Issue 911126 link

Starred by 1 user
Status: Assigned
Owner:
█ phoglund@chromium.org
Last visit > 30 days ago
Cc:
█ chromium...@skia-public.iam.gserviceaccount.com
█ phoglund@chromium.org
maxlg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-237.3% regression in rendering.mobile/avg_surface_fps at 605673:612530

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

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

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

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


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
Project Member

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/13dae4c2140000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Dec 7 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/15d1b784140000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jan 14 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/16b92b7d940000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jan 14

Cc: phoglund@chromium.org chromium...@skia-public.iam.gserviceaccount.com
Owner: phoglund@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/1599562d940000

Roll src/third_party/catapult cc4ed36d5b76..662c038f3fdd (1 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/2e38d313a49bc8c28b8ce38f004776dbf4357b99
thread_total_all_cpu_time_per_frame: No values → 23.16

Revert "Add more information to |error| of -didFailFavigationWithSSLError:." by phoglund@chromium.org
https://chromium.googlesource.com/chromium/src/+/87db0e76078d63cad178c06262438ba5ae9351b4
thread_total_all_cpu_time_per_frame: 23.16 → 22.99 (-0.1723)

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

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

Sign in to add a comment