New issue
Advanced search Search tips

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

6.2% regression in system_health.memory_mobile at 600154:600217

Project Member Reported by hjd@google.com, Oct 19

Issue description

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

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


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/124ddbcae40000

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: 9.359e+07 → 1.007e+08 (+7.08e+06)

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