New issue
Advanced search Search tips

Issue 681631 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

54.3% regression in scheduler.tough_scheduling_cases at 443667:443758

Project Member Reported by nzolghadr@chromium.org, Jan 16 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=681631

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


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

chromium-rel-win10
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 17 2017

Mergedinto: 681595
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : flackr
  Commit : 96f33ef6f7c21303a68dc52c3e27a925fb200ce5
  Date   : Fri Jan 13 22:05:44 2017
  Subject: Revert "Round the scroll offset synced back to main instead of flooring." and disable CompositeOpaqueFixedPosition

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : queueing_durations/queueing_durations
  Change       : 44.06% | 0.0808936203943 -> 0.116536370963

Revision             Result                       N
chromium@443667      0.0808936 +- 0.00242578      6      good
chromium@443690      0.080947 +- 0.00251032       6      good
chromium@443691      0.120009 +- 0.00310697       6      bad       <--
chromium@443692      0.118106 +- 0.00361642       6      bad
chromium@443693      0.117514 +- 0.00184562       6      bad
chromium@443696      0.121456 +- 0.00397498       6      bad
chromium@443702      0.119398 +- 0.00389282       6      bad
chromium@443713      0.12005 +- 0.00296952        6      bad
chromium@443758      0.116536 +- 0.0031813        6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests scheduler.tough_scheduling_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990287308245253088

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5878088149237760


| 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