New issue
Advanced search Search tips

Issue 917225 link

Starred by 1 user
Status: Duplicate
Merged: issue 914365
Owner:
eseckler@google.com
Closed: Dec 21
Cc:
kouhei@chromium.org
eseckler@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7% regression in rendering.mobile/tasks_per_frame_total_all at 615562:615610

Project Member Reported by kouhei@google.com, Dec 21 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 21 

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

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


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

Android Nexus6 WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 21

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

trace writer: Send patches after completing fragmented packet by eseckler@google.com
https://android.googlesource.com/platform/external/perfetto/+/15697965801191b657fa3213139ff8532b2e6cc7
tasks_per_frame_total_all: 32.3 → 34.58 (+2.286)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by eseckler@chromium.org, Dec 21

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

Sign in to add a comment