New issue
Advanced search Search tips

Issue 896358 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 22
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

24.6% regression in system_health.memory_mobile at 600154:600217

Project Member Reported by sullivan@chromium.org, Oct 17

Issue description

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

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


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

Android Nexus5 Perf

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

Reland gpu: Add UMA metric for measuring total raster task duration. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/cd8fbb77cfa164eef66378204a588443af9bb875
memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size: 7.121e+07 → 8.987e+07 (+1.865e+07)

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

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

Sign in to add a comment