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

Issue 886890 link

Starred by 1 user
Status: Duplicate
Merged: issue 888558
Owner: ----
Closed: Sep 24
Cc:
oysteine@google.com
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.6% regression in memory.top_10_mobile at 592107:592170

Project Member Reported by alexclarke@chromium.org, Sep 19 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 19 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=886890

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


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

Android Nexus5X WebView Perf

memory.top_10_mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 20

Cc: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17c7f313640000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/0f374eff414ec0683aafbe2aae3fd405a4fcc221
1.008e+08 → 1.019e+08 (+1.163e+06)

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

Benchmark documentation link:
  None

Comment 4 by pasko@chromium.org, Sep 24

Mergedinto: 888558
Status: Duplicate (was: Assigned)
►

Sign in to add a comment