New issue
Advanced search Search tips

Issue 871937 link

Starred by 1 user
Status: Fixed
Owner:
ericrk@chromium.org
Closed: Aug 13
Cc:
ericrk@chromium.org
chiniforooshan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8% regression in system_health.memory_desktop at 579609:579685

Project Member Reported by chiniforooshan@chromium.org, Aug 7 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 7 

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

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


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

Win 7 Nvidia GPU Perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 7

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

Temporarily disable mip generation to investigate mem regression by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/6be4fea2cd3ada5d66d625aca464c50f0bf9fb4f
1.377e+07 → 1.494e+07 (+1.177e+06)

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

Comment 4 by ericrk@chromium.org, Aug 13

Status: Fixed (was: Assigned)
The change in question has been reverted - it was a temporary experiment and the regression was expected.
►

Sign in to add a comment