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

Issue 727512 link

Starred by 1 user
Status: WontFix
Owner:
█ fsam...@chromium.org
Last visit > 30 days ago
Closed: Jun 2017
Cc:
█ fsam...@chromium.org
toyoshim@chromium.org
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

405.7%-989.8% regression in thread_times.key_idle_power_cases at 474753:474857

Project Member Reported by toyoshim@chromium.org, May 30 2017 
See the link to graphs below.
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 30 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/request-animation-frame.html


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=request.animation.frame.html thread_times.key_idle_power_cases

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

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


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, May 30 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/request-animation-frame.html


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=request.animation.frame.html thread_times.key_idle_power_cases

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

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


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, May 30 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : thread_total_all_cpu_time_per_second/blank.html


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=blank.html thread_times.key_idle_power_cases

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

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


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, May 30 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : thread_total_all_cpu_time_per_second/blank.html


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=blank.html thread_times.key_idle_power_cases

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

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


| 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 Speed>Bisection.  Thank you!

Comment 10 by toyoshim@chromium.org, May 31 2017

Components: Speed>Bisection
Bisect failed for unknown reasons

test results on ToT seem to go back to the original level, and can be closed as WontFix. But FYI for bisect failing.
Project Member

Comment 12 by 42576172...@developer.gserviceaccount.com, Jun 13 2017

Cc: fsam...@chromium.org
Owner: fsam...@chromium.org

=== Auto-CCing suspected CL author fsamuel@chromium.org ===

Hi fsamuel@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : fsamuel
  Commit : d71466ad118aca05aa347c9766f80a5f77528588
  Date   : Thu May 25 20:35:22 2017
  Subject: cc::SurfaceDependencyTracker should not crash when a Display goes away

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : thread_total_all_cpu_time_per_second/set-timeout.html
  Change       : 260.55% | 0.598721270183 -> 2.15870016202

Revision             Result                     N
chromium@474752      0.598721 +- 0.0711691      6      good
chromium@474779      0.647192 +- 0.142134       6      good
chromium@474781      0.619634 +- 0.106558       6      good
chromium@474782      0.615532 +- 0.0549773      6      good
chromium@474783      1.90806 +- 0.275894        6      bad       <--
chromium@474786      2.13231 +- 0.439527        6      bad
chromium@474792      2.05021 +- 0.455021        6      bad
chromium@474805      1.9787 +- 0.302439         6      bad
chromium@474857      2.1587 +- 0.524708         6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html thread_times.key_idle_power_cases

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

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


| 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 Speed>Bisection.  Thank you!

Comment 13 by fsam...@chromium.org, Jun 14 2017

Status: WontFix (was: Untriaged)
Should be back to normal levels ToT after I landed https://codereview.chromium.org/2917743002/
►

Sign in to add a comment