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

Issue 912650 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

2.3%-37.6% regression in cpu_time_percentage,memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size at 614130:614204

Project Member Reported by 42576172...@developer.gserviceaccount.com, Dec 6

Issue description

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

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


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.common_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

memory.desktop - Benchmark documentation link:
  None
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/17f7696a140000

OOP-R: GrContext::flush and glFlush at every DoRasterCHROMIUM by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/b2615d69395f6922a2d5b727045cfd70b73445fe
cpu_time_percentage: 0.5416 → 0.7535 (+0.2118)

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

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

Sign in to add a comment