New issue
Advanced search Search tips

Issue 918605 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Jan 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.9%-118.9% regression in rendering.mobile/thread_raster_cpu_time_per_frame at 618319:618547

Project Member Reported by lanwei@chromium.org, Jan 2

Issue description

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: wangxianzhu@chromium.org
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15d55a72940000

[PE] Fix SVGImage performance regression by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/a465e8196b0d3b34cdc2e3acb7b8e79a1d0e4591
thread_raster_cpu_time_per_frame: 0.6334 → 1.292 (+0.6589)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Mergedinto: 918610
Status: Duplicate (was: Assigned)

Sign in to add a comment