New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 847451 link

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



Sign in to add a comment

36.7% regression in thread_times.tough_compositor_cases at 559975:560116

Project Member Reported by kraynov@chromium.org, May 29 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 29 2018 

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

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


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

chromium-rel-win10
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 30 2018

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

Do not consider pending queries as idle work in passthrough decoder by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/ef1b3ab1cc2498425c46c021e9344c514392026c

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

Sign in to add a comment