New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 903358 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

34.3%-36.8% improvement in rendering.desktop/thread_raster_cpu_time_per_frame at 605609:605629

Project Member Reported by alexclarke@chromium.org, Nov 8

Issue description

Suspiciously large improvement, did something break?
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=903358

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

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

lookup sent types using factory pointer by mtklein@chromium.org
https://skia.googlesource.com/skia/+/abdba8f8f03d11ff89a3258465d1386950fe985e
thread_raster_cpu_time_per_frame: 1.42 → 0.9273 (-0.4926)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: enne@chromium.org
:)
Status: WontFix (was: Assigned)
Cc: khushals...@chromium.org
!!!
Yay! Thanks Mike. :)

Sign in to add a comment