New issue
Advanced search Search tips

Issue 913582 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.3%-9.5% regression in system_health.memory_desktop at 614130:614204

Project Member Reported by npm@chromium.org, Dec 10

Issue description

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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: ccameron@chromium.org
Owner: ccameron@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14a74312140000

OOP-R: GrContext::flush and glFlush at every DoRasterCHROMIUM by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/b2615d69395f6922a2d5b727045cfd70b73445fe
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 3.385e+07 → 3.788e+07 (+4.027e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Sign in to add a comment