New issue
Advanced search Search tips

Issue 883755 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Sep 26
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-4.4% regression in system_health.memory_mobile at 585740:585770

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=883755

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


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

Android Nexus6 WebView Perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: herb@google.com
Owner: herb@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12acd0d3640000

Simplify lifetime of scaler context for remote cache by herb@google.com
https://skia.googlesource.com/skia/+/b2c721667f74e0505a35481bd8b109c74be09f98
2.282e+07 → 2.366e+07 (+8.424e+05)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Mergedinto: 877609
Status: Duplicate (was: Assigned)

Sign in to add a comment