New issue
Advanced search Search tips

Issue 862235 link

Starred by 1 user
Status: Assigned
Owner:
sadrul@chromium.org
Cc:
sadrul@chromium.org
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

129.5%-155.7% regression in mean_frame_time_renderer_compositor at 571367:571421

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 10 

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 10

Cc: sadrul@chromium.org
Owner: sadrul@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12cf451aa40000

perf: Fix thread-times/rendering benchmarks. by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/5f4b7cd215d126758e347e89f771dd5d6db8607c
0 → 48.6 (+48.6)

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

Sign in to add a comment