New issue
Advanced search Search tips

Issue 842274 link

Starred by 1 user
Status: WontFix
Owner:
penghuang@chromium.org
Closed: May 2018
Cc:
penghuang@chromium.org
sadrul@chromium.org
piman@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.6%-4.3% regression in thread_times.tough_compositor_cases at 557530:557595

Project Member Reported by majidvp@chromium.org, May 11 2018 
There is an earlier improvement but it is of a larger
magnitude so they may be unrelated. Let's see if pin-point
finds a good suspect.
Project Member

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

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 11 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/17d5ebf7c40000

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

Comment 4 by penghuang@chromium.org, May 14 2018

Cc: sadrul@chromium.org piman@chromium.org
Status: WontFix (was: Assigned)
It is expected result. The change will add one task per SwapBuffers() for running presentation callback. I think we don't need fix it.
►

Sign in to add a comment