New issue
Advanced search Search tips

Issue 883752 link

Starred by 1 user
Status: Duplicate
Merged: issue 880421
Owner:
ericrk@chromium.org
Closed: Sep 18
Cc:
npm@chromium.org
ericrk@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.6%-43.8% regression in rendering.mobile at 588274:588276

Project Member Reported by npm@chromium.org, Sep 13 
See the link to graphs below.
Project Member

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

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

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


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, Sep 13

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

Revert "Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers" by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/6eb9eee331affe92c52a2926f57422bcbf40fa43
568.6 → 703.1 (+134.5)

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

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

Comment 4 by ericrk@chromium.org, Sep 18

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

Sign in to add a comment