New issue
Advanced search Search tips

Issue 918707 link

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



Sign in to add a comment

66.4% regression in rendering.desktop/thread_raster_cpu_time_per_frame at 618817:618831

Project Member Reported by chiniforooshan@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=918707

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


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

Win 7 Perf

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

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

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/11d7f726940000

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

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