New issue
Advanced search Search tips

Issue 923376 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.9%-34.9% regression in rendering.desktop/tasks_per_frame_total_all at 623484:623582

Project Member Reported by tdres...@chromium.org, Jan 18 (4 days ago)

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 18 (4 days ago)

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=923376

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


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

linux-perf
mac-10_12_laptop_low_end-perf

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

Comment 2 by 42576172...@developer.gserviceaccount.com, Jan 18 (4 days ago)

Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 18 (4 days ago)

Cc: rockot@google.com
Owner: rockot@google.com
Status: Assigned (was: Unconfirmed)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/10038f8a540000

[mojo] Per-message dispatch tasks by rockot@google.com
https://chromium.googlesource.com/chromium/src/+/471aa794bbb9e3a98542ee2135ea61ddf4bf87a3
thread_raster_cpu_time_per_frame: 0.6419 → 0.7842 (+0.1423)

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

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

Sign in to add a comment