New issue
Advanced search Search tips

Issue 883813 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

1.4%-2.2% regression in system_health.memory_desktop at 589948:590046

Project Member Reported by npm@chromium.org, Sep 13

Issue description

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

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


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

Win 7 Nvidia GPU Perf
mac-10_12_laptop_low_end-perf

memory.desktop - Benchmark documentation link:
  None

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/155646b5640000

Roll src/third_party/skia 10494e34e453..a2bc1ca21bbc (1 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/0ecd7737d89b3890072eb5eab1cff70f2eaca579
1.836e+07 → 1.873e+07 (+3.677e+05)

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

Benchmark documentation link:
  None
Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner

Sign in to add a comment