New issue
Advanced search Search tips

Issue 901392 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 897111
Owner:
Closed: Nov 5
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

23.7% regression in rendering.desktop/thread_raster_cpu_time_per_frame at 599962:600091

Project Member Reported by tdres...@chromium.org, Nov 2

Issue description

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

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


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

Win 7 Perf

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

Stop using color space xform canvas in Skia's picture backed images by brianosman@google.com
https://chromium.googlesource.com/chromium/src/+/530a1ad5eb14f098bc897aecce9f8d9cdc099ec1
thread_raster_cpu_time_per_frame: 0.0857 → 0.1088 (+0.02309)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: mtkl...@google.com
Mergedinto: 897111
Status: Duplicate (was: Assigned)

Sign in to add a comment