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

Issue 903131 link

Starred by 1 user
Status: Assigned
Owner:
js...@chromium.org
Cc:
js...@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1% regression in memory.desktop at 603394:603432

Project Member Reported by alexclarke@chromium.org, Nov 8 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 8 

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

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


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

Win 7 Nvidia GPU Perf

memory.desktop - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 8

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

Roll ICU to ICU 63.1 + Chromium patches by jshin@chromium.org
https://chromium.googlesource.com/chromium/src/+/5afd3007276ae994a1c9fc5bb7da7363babb76e3
memory:chrome:all_processes:reported_by_chrome:malloc:effective_size: 1.514e+07 → 1.523e+07 (+8.147e+04)

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

Benchmark documentation link:
  None
►

Sign in to add a comment