New issue
Advanced search Search tips

Issue 715854 link

Starred by 1 user
Status: Duplicate
Merged: issue 714966
Owner:
horo@chromium.org
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9.3% regression in service_worker.service_worker_micro_benchmark at 465977:466068

Project Member Reported by horo@chromium.org, Apr 27 2017 
See the link to graphs below.

Comment 1 by horo@chromium.org, Apr 27 2017 

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

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


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

chromium-rel-mac11-pro

Comment 3 by horo@chromium.org, Apr 27 2017

Components: Blink>ServiceWorker
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 27 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile

Revision             Result                   N
chromium@465976      2.45214 +- 0.249557      21      good
chromium@466068      2.40905 +- 0.256965      21      bad

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

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

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


| 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 6 by 42576172...@developer.gserviceaccount.com, Apr 27 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile

Revision             Result                   N
chromium@465976      2.48071 +- 0.214975      21      good
chromium@466068      2.44905 +- 0.217901      21      bad

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

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

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


| 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, Apr 27 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile

Revision             Result                   N
chromium@465976      2.45214 +- 0.249557      21      good
chromium@466068      2.40905 +- 0.256965      21      bad

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

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

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


| 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 10 by 42576172...@developer.gserviceaccount.com, Apr 27 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile

Revision             Result                  N
chromium@465976      2.45 +- 0.268142        21      good
chromium@466068      2.50167 +- 0.43734      21      bad

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

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

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


| 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 11 by nhiroki@chromium.org, Apr 28 2017

Cc: -horo@chromium.org
Owner: horo@chromium.org
Status: Assigned (was: Untriaged)
We cannot find a culprit and the diff is quite small (about 0.1 ms), so can we mark this with WONTFIX?

horo@, any thoughts?
Project Member

Comment 15 by 42576172...@developer.gserviceaccount.com, Apr 28 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile

Revision             Result                  N
chromium@465976      2.49595 +- 0.75745      21      good
chromium@466068      2.4519 +- 0.322372      21      bad

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

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

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


| 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 16 by 42576172...@developer.gserviceaccount.com, Apr 28 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile

Revision             Result                    N
chromium@465976      1.16048 +- 0.0651555      21      good
chromium@466068      1.1569 +- 0.0572172       21      bad

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

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

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


| 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 17 by 42576172...@developer.gserviceaccount.com, Apr 28 2017

Mergedinto: 714966
Status: Duplicate (was: Assigned)

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

Suspected Commit
  Author : shimazu
  Commit : 1ac68cf90fa046d3e9c1418aee7cd14b8ec38210
  Date   : Thu Apr 20 06:03:46 2017
  Subject: ServiceWorker: Use mojo's data pipe for respondWith(stream)

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile
  Change       : 8.25% | 1.06 -> 1.1475

Revision             Result                    N
chromium@465906      1.06 +- 0.0158114         6      good
chromium@465908      1.06333 +- 0.0182574      6      good
chromium@465909      1.16417 +- 0.0268483      6      bad       <--
chromium@465912      1.16333 +- 0.0378594      6      bad
chromium@465917      1.15417 +- 0.0268483      6      bad
chromium@465927      1.15667 +- 0.0182574      6      bad
chromium@465947      1.17 +- 0.0308221         6      bad
chromium@465987      1.16167 +- 0.033665       6      bad
chromium@466068      1.1475 +- 0.0183712       6      bad

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

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

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


| 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!
►

Sign in to add a comment