New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 886891 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 888558
Owner: ----
Closed: Sep 24
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.6%-4.4% regression in memory.top_10_mobile at 592107:592170

Project Member Reported by alexclarke@chromium.org, Sep 19

Issue description

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

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


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

Android Nexus5X WebView Perf

memory.top_10_mobile - Benchmark documentation link:
  None
Cc: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/113673c0e40000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/0f374eff414ec0683aafbe2aae3fd405a4fcc221
3.651e+07 → 3.733e+07 (+8.195e+05)

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

Benchmark documentation link:
  None
Mergedinto: 888558
Status: Duplicate (was: Assigned)

Sign in to add a comment