New issue
Advanced search Search tips

Issue 734930 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

46.2% regression in service_worker.service_worker_micro_benchmark at 479396:479508

Project Member Reported by falken@chromium.org, Jun 20 2017

Issue description

See the link to graphs below.
 

Comment 1 by falken@chromium.org, Jun 20 2017

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

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


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

chromium-rel-mac12

Comment 3 by falken@chromium.org, Jun 20 2017

Components: Blink>ServiceWorker
Labels: -Pri-2 Pri-1
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jun 20 2017


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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_90_percentile/concurrent_1_response_90_percentile

Revision             Result                   N
chromium@479395      2.15357 +- 0.626943      21      good
chromium@479508      2.26738 +- 1.8127        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/8976285224523829168

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


| 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, Jun 20 2017


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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_90_percentile/concurrent_1_response_90_percentile

Revision             Result                   N
chromium@479395      2.11929 +- 0.258581      21      good
chromium@479508      2.11952 +- 0.237687      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/8976279562550401680

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


| 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 7 by falken@chromium.org, Jun 23 2017

Status: WontFix (was: Untriaged)
The graph definitely got more variable.

I don't see an obvious culprit in the revision log.

The other platform don't seem to have a regression here.

Don't think we can do anything further.


Comment 8 by falken@chromium.org, Jun 23 2017

 Issue 735287  has been merged into this issue.

Sign in to add a comment