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

Issue 792948 link

Starred by 1 user
Status: Fixed
Owner:
█ junov@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
█ junov@chromium.org
█ xlai@chromium.org
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.7% regression in scheduler.tough_scheduling_cases at 521749:521898

Project Member Reported by npm@chromium.org, Dec 7 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

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

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


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

chromium-rel-mac11-pro
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14838b1c040000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Dec 7 2017

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

Move TransferableResource creation to Canvas Resource
By junov@chromium.org · Tue Dec 05 22:44:49 2017
chromium @ 4f6bce25c2f94e59611343ddab1fffcc13f79f07

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

Comment 6 by junov@chromium.org, Dec 14 2017

Status: Fixed (was: Assigned)
The regression introduced by my cl was fixed with: https://chromium.googlesource.com/chromium/src.git/+/ec6125cd13b1850ece40029cff8c4504db7f7c43

But not all the graphs associate with this bug have recovered.  This issue needs to be forked IMHO.  I'm not sure how to use chromeperf correctly. 

@npm: could you create another bug associate with just the graph for: ChromiumPerf/chromium-rel-win8-dual/scheduler.tough_scheduling_cases / queueing_durations /

It is a separate bug and needs a standalone pinpoint job to find the right culprit CL.

Comment 7 by npm@chromium.org, Jan 2 2018 

Sorry was on vacation. Created  issue 798424 , thanks for letting me know.
►

Sign in to add a comment