New issue
Advanced search Search tips

Issue 918604 link

Starred by 2 users
Status: WontFix
Owner:
eseckler@chromium.org
Closed: Jan 3
Cc:
eseckler@chromium.org
skyos...@chromium.org
oysteine@chromium.org
lanwei@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.1%-21% regression in rendering.mobile/percentage_smooth at 617015:618486

Project Member Reported by lanwei@chromium.org, Jan 2 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 2 

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

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


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

Android Nexus6 WebView Perf
android-nexus5x-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 3

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

tracing: Emit metadata at the end of tracing instead of beginning by eseckler@chromium.org
https://chromium.googlesource.com/chromium/src/+/e49e90a64dbbd25089c1faf972312a9ed4c08b34
tasks_per_frame_total_all: 88.19 → 98.42 (+10.24)

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

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

Comment 4 by eseckler@chromium.org, Jan 3

Cc: oysteine@chromium.org skyos...@chromium.org
Status: WontFix (was: Assigned)
The change above is expected to cause slight metric changes in either direction, as it makes the tracing data + calculated metrics more accurate. WAI.
►

Sign in to add a comment