New issue
Advanced search Search tips

Issue 880310 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 13
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 4% regression in rendering.mobile at 587661:587775

Project Member Reported by maxlg@chromium.org, Sep 4

Issue description

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: sunn...@chromium.org
Owner: sunn...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15dbdf5d640000

Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/370c8bc2082a3665ccc45fef39955fd550170b61
0.6581 → 4.083 (+3.425)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Status: WontFix (was: Assigned)
The above CL was reverted, and relanded with important fixes to fix incorrect rendering.  Those fixes should also mitigate these regressions.
Thanks for taking a look.

Sign in to add a comment