New issue
Advanced search Search tips

Issue 918545 link

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



Sign in to add a comment

6.7%-77% regression in rendering.mobile/tasks_per_frame_total_all at 618794:618847

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=918545

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


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

Android Nexus5X WebView Perf
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 2

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

Update shadow blur-radius computations by fmalita@chromium.org
https://chromium.googlesource.com/chromium/src/+/909793b85dd2eb0bd37954ec50fbc86d547be50a
thread_raster_cpu_time_per_frame: 0.9513 → 1.26 (+0.3088)

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

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

Comment 4 by fmalita@chromium.org, Jan 3

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

Sign in to add a comment