New issue
Advanced search Search tips

Issue 844527 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.5%-4% regression in thread_times.tough_compositor_cases at 557293:557642

Project Member Reported by npm@chromium.org, May 18 2018

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

chromium-rel-win10
linux-perf
Project Member

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

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

PresentationCallback: Fix a TODO in viz::Display by penghuang@chromium.org
https://chromium.googlesource.com/chromium/src/+/7ef949f51ec608a970a51f86c568d52f3e5ec959

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
It is expected result. We need post one task per frame for receiving presentation feedback in message loop.

Sign in to add a comment