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

Issue 914851 link

Starred by 1 user
Status: Assigned
Owner:
samans@chromium.org
Cc:
perezju@chromium.org
sullivan@google.com
█ kbr@chromium.org
samans@chromium.org
rjkroege@chromium.org
bradhall@chromium.org
ericrk@chromium.org
piman@chromium.org
nedngu...@google.com
jbudorick@chromium.org
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 882591



Sign in to add a comment

1.9%-3.9% regression in avg_surface_fps,frame_times at 615729:615788

Project Member Reported by 42576172...@developer.gserviceaccount.com, Dec 13 
See the link to graphs below.
Project Member

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

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

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


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

Android Nexus6 WebView Perf

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

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

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

Use SharedImage in WebGL's DrawingBuffer by samans@chromium.org
https://chromium.googlesource.com/chromium/src/+/bce53252ce5ded76582c9a27a499bda2249052fc
frame_times: 18.37 → 18.83 (+0.4693)

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

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

Comment 4 by samans@chromium.org, Dec 13

Blocking: 882591
Cc: rjkroege@chromium.org kbr@chromium.org piman@chromium.org ericrk@chromium.org

Comment 5 by kbr@chromium.org, Dec 13 

It looks like only the Android Nexus6 WebView Perf bot originally alerted, correct? If that's true then I think this should be closed as WontFix - that hardware is obsolete.

Comment 6 by kbr@chromium.org, Dec 13

Components: Internals>GPU>Internals Mobile>WebView

Comment 7 by sullivan@google.com, Dec 13

Cc: nednguyen@chromium.org
Ned, do you know who to ask if that bot should still be running if it's obsolete?

Comment 8 by nedngu...@google.com, Dec 14

Cc: bradhall@chromium.org perezju@chromium.org jbudorick@chromium.org
In general, I think that would be CCI and/or Telemetry team. For now, I would ask Juan for Android bot.

Comment 9 by nedngu...@google.com, Dec 14

Cc: -nednguyen@chromium.org nedngu...@google.com

Comment 10 by perezju@chromium.org, Dec 14 

If I remember correctly the plan is to remove that bot:
https://docs.google.com/document/d/1ROjKRmJlK_G5JXvsPs8Qq026JwYXkmrFP8pnZoffHEs/edit?ts=5adf6d68#

the replacement pixel2 and go webview bots are in perf.fyi; where still some failures need to be ironed out.
►

Sign in to add a comment