New issue
Advanced search Search tips

Issue 875911 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 873883
Owner:
Closed: Aug 27
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.3%-115.5% regression in avg_surface_fps,frame_times,mean_frame_time,mean_frame_time_renderer_compositor,mean_input_event_latency,mean_main_thread_scroll_latency,percentage_smooth,tasks_per_frame_total_all,thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 576404:583986

Project Member Reported by 42576172...@developer.gserviceaccount.com, Aug 20

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus5X WebView Perf
android-nexus5x-perf
Cc: chrishtr@chromium.org
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16f8d31a640000

[PE] Stop dirtying compositing inputs on any layout for the root PaintLayer. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/46520ae13478333fe882e79041b667e5a3112796
0.07206 → 0.151 (+0.07894)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 873883
Status: Duplicate (was: Assigned)

Sign in to add a comment