New issue
Advanced search Search tips

Issue 917231 link

Starred by 1 user
Status: Duplicate
Owner:
piman@chromium.org
Closed: Jan 2
Cc:
kouhei@chromium.org
piman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

25.1% regression in rendering.mobile/tasks_per_frame_total_all at 607369:607616

Project Member Reported by kouhei@google.com, Dec 21 
See the link to graphs below.
Project Member

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

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

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


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 21

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

Use SharedImageInterface for one-copy staging buffers by piman@chromium.org
https://chromium.googlesource.com/chromium/src/+/9058f7866e74b92eeef1c30780522fba0740d2f3
tasks_per_frame_total_all: 96.73 → 127.7 (+30.99)

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

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

Comment 4 by piman@google.com, Jan 2

Mergedinto: 905019
Status: Duplicate (was: Assigned)
►

Sign in to add a comment