New issue
Advanced search Search tips

Issue 879204 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.1%-2.6% regression in system_health.memory_mobile at 587172:587302

Project Member Reported by mustaq@chromium.org, Aug 30

Issue description

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

memory.top_10_mobile - Benchmark documentation link:
  None
Cc: ericrk@chromium.org
Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/146ee5f5640000

Android OOP-D: Enable OOP-D for Android Waterfall by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/86da5de5d854b46ef4e85bbef645a1c0866ed13b
1.475e+08 → 1.505e+08 (+3.037e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 881466
Status: Duplicate (was: Assigned)

Sign in to add a comment