New issue
Advanced search Search tips

Issue 895387 link

Starred by 1 user
Status: Fixed
Owner:
penghuang@chromium.org
Closed: Oct 16
Cc:
penghuang@chromium.org
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1%-510.3% regression in memory.desktop at 599275:599339

Project Member Reported by npm@chromium.org, Oct 15 
Some graphs mirror an improvement, but others don't.
Project Member

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

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

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


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

linux-perf

memory.desktop - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 15

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

Skia: Enable ExplicitlyAllocateGPUResources & SortRenderTargets. by penghuang@chromium.org
https://chromium.googlesource.com/chromium/src/+/0cb762482ab99e54be75368d8da949d52af00059
memory:chrome:all_processes:reported_by_chrome:skia:effective_size: 4.219e+07 → 2.69e+08 (+2.268e+08)

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

Benchmark documentation link:
  None
►

Sign in to add a comment