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

Issue 879601 link

Starred by 2 users
Status: Assigned
Owner:
lethalantidote@chromium.org
Cc:
█ hubbe@chromium.org
mlamouri@chromium.org
lethalantidote@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.2% regression in media.desktop at 587766:587825

Project Member Reported by hubbe@google.com, Aug 31 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 31 

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

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


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

mac-10_13_laptop_high_end-perf

media.desktop - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 31

Cc: lethalantidote@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11dd52c9640000

Moves cc::Surfaces for Videos onto its own thread. by lethalantidote@chromium.org
https://chromium.googlesource.com/chromium/src/+/79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6
1.579e+07 → 1.62e+07 (+4.151e+05)

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

Comment 4 by hubbe@chromium.org, Aug 31

Cc: -lethalantidote@chromium.org hubbe@chromium.org
Owner: lethalantidote@chromium.org

Comment 5 by hubbe@chromium.org, Aug 31

Cc: lethalantidote@chromium.org
 Issue 879600  has been merged into this issue.

Comment 6 by hubbe@chromium.org, Aug 31 

 Issue 879599  has been merged into this issue.

Comment 7 by hubbe@chromium.org, Aug 31 

 Issue 879614  has been merged into this issue.

Comment 8 by hubbe@chromium.org, Aug 31 

 Issue 879612  has been merged into this issue.

Comment 9 by lethalantidote@chromium.org, Aug 31

Cc: mlamouri@chromium.org

Comment 10 by hubbe@chromium.org, Aug 31 

 Issue 879603  has been merged into this issue.
 Issue 879615  has been merged into this issue.
 Issue 879616  has been merged into this issue.
Issue 879635 has been merged into this issue.
Issue 879636 has been merged into this issue.
Issue 879637 has been merged into this issue.
Issue 879639 has been merged into this issue.

Comment 11 by hubbe@chromium.org, Sep 4 

 Issue 879712  has been merged into this issue.

Comment 12 by hubbe@chromium.org, Sep 4 

 Issue 879715  has been merged into this issue.

Comment 13 by hubbe@chromium.org, Sep 4 

 Issue 879716  has been merged into this issue.

Comment 14 by hubbe@chromium.org, Sep 4 

 Issue 879717  has been merged into this issue.

Comment 15 by mlamouri@chromium.org, Sep 5 

Looking at the traces, it seems that we have one more CC resource which may be the cause for the increased memory. I'm not sure if that's just a timing issue or a side effect of the change. lethalantidote@ WDYT?
►

Sign in to add a comment