New issue
Advanced search Search tips

Issue 896812 link

Starred by 2 users
Status: Assigned
Owner:
reed@google.com
Cc:
maxlg@chromium.org
sullivan@chromium.org
reed@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.7%-89.6% regression in percentage_smooth,tasks_per_frame_total_all,thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 600478:600567

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 18 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 18 

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

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


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

Android Nexus5 Perf
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, Oct 18

Cc: reed@google.com
Owner: reed@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1536b6bce40000

remove flag for SK_SUPPORT_LEGACY_TILED_BITMAPS by reed@google.com
https://chromium.googlesource.com/chromium/src/+/ad47e94ecb458e1df970410c9d12e599009bd190
thread_raster_cpu_time_per_frame: 15.34 → 28.72 (+13.38)

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

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

Comment 4 by maxlg@chromium.org, Nov 20

Cc: maxlg@chromium.org
 Issue 898911  has been merged into this issue.
►

Sign in to add a comment