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

Issue 825608 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.3%-2.2% regression in system_health.memory_desktop at 545055:545153

Project Member Reported by sullivan@chromium.org, Mar 25 2018

Issue description

Note that significant improvements were found at the same range: https://chromeperf.appspot.com/group_report?sid=a9ee828e59f75f97520cfc70ca8b8c0b4e32c19c699f42b0115c156365439f88

When a culprit is found, we should consider whether it is a net positive.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 25 2018

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

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


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

chromium-rel-mac11-pro
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 25 2018

Cc: primiano@chromium.org erikc...@chromium.org ajwong@chromium.org
Owner: erikc...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/148f49e3440000

Correct macOS private memory footprint calculations. by erikchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/7c1d03f55ec7a248aece22abfdef25e100bcf4f4

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
WAI - this was an accounting change.

Sign in to add a comment