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

Issue 669180 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.4% regression in scheduler.tough_scheduling_cases at 434231:434299

Project Member Reported by benhenry@chromium.org, Nov 28 2016

Issue description

Graphs included below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=669180

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg29rN4wgM


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

chromium-rel-mac-hdd
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 29 2016

Mergedinto: 669172
Status: Duplicate (was: Untriaged)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Update ts_proxy to latest commit
Author  : nednguyen
Commit description:
  
For all the changes, see: https://github.com/WPO-Foundation/tsproxy/compare/6fae6141104d077c8ceb1136b6ddee5b98f30240...9ae7d2ff822cb7cef15bc54ff614273c99691744

The main change is "Reduced CPU impact when idle or running in bypass mode".

Bug: https://code.google.com/p/chrome-os-partner/issues/detail?id=60009

BUG=chromium:653519

Review-Url: https://codereview.chromium.org/2516973005
Commit  : 4e71cc39324b205febf5a4cfa3a089a1e2aeab74
Date    : Wed Nov 23 17:55:09 2016


===== TESTED REVISIONS =====
Revision                             Mean      Std Dev  N      Good?
chromium@434230                      0.122165  88.0185  38352  good
chromium@434248                      0.121174  87.6889  38338  good
chromium@434248,catapult@982d024dad  0.120538  88.234   38362  good
chromium@434248,catapult@4e71cc3932  0.135222  95.9606  38347  bad    <--
chromium@434249                      0.134319  95.8479  38353  bad
chromium@434250                      0.134094  96.0646  38354  bad
chromium@434251                      0.134706  95.5737  38365  bad
chromium@434253                      0.136637  97.304   38314  bad
chromium@434257                      0.135582  96.5539  38318  bad
chromium@434265                      0.13624   96.5328  38299  bad
chromium@434299                      0.134079  95.9666  38343  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 669180

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: queueing_durations/queueing_durations
Relative Change: 9.75%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/892
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994716902263674816


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5272059192541184

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Sign in to add a comment