New issue
Advanced search Search tips

Issue 916573 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 915769
Owner:
Closed: Dec 19
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3%-5.4% regression in system_health.memory_mobile at 616478:616574

Project Member Reported by mustaq@chromium.org, Dec 19

Issue description

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

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


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

android-nexus5x-perf

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

[TaskScheduler]: Disable MergeBlockingNonBlockingPools from fieldtrial_testing_config. by etiennep@chromium.org
https://chromium.googlesource.com/chromium/src/+/ad3c94a2279bd7584003990858339a94f69a838b
memory:chrome:all_processes:reported_by_chrome:malloc:effective_size: 5.085e+07 → 5.328e+07 (+2.435e+06)

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

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

Sign in to add a comment