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

Issue 874872 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9.5% regression in system_health.memory_desktop at 580571:580745

Project Member Reported by tdres...@chromium.org, Aug 16

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=874872

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


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

mac-10_12_laptop_low_end-perf
Cc: farahcharab@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14adc82c640000

Scheduler: Extend resource fetch priority experiment to loading only. by farahcharab@google.com
https://chromium.googlesource.com/chromium/src/+/bac05e51eb8937e213689a3e190acd697467eef6
2.376e+07 → 2.588e+07 (+2.114e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner

Sign in to add a comment