New issue
Advanced search Search tips

Issue 897711 link

Starred by 1 user
Status: Duplicate
Merged: issue 897710
Owner: ----
Closed: Oct 22
Cc:
andrescj@chromium.org
hjd@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

64.4% regression in system_health.memory_desktop at 600107:600257

Project Member Reported by hjd@google.com, Oct 22 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 22 

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

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


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

Win 7 Nvidia GPU Perf

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

Comment 3 by hjd@google.com, Oct 22

Mergedinto: 897710
Status: Duplicate (was: Untriaged)
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Oct 22

Cc: andrescj@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15ec1026e40000

Disallow libjpeg_turbo downscaling of images with non-whole MCUs. by andrescj@chromium.org
https://chromium.googlesource.com/chromium/src/+/8b9172a61f4e507b2eef30b2af438d2c19c0992d
memory:chrome:all_processes:reported_by_chrome:skia:effective_size: 7.281e+05 → 1.157e+06 (+4.293e+05)

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

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

Sign in to add a comment