New issue
Advanced search Search tips

Issue 651619 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

28.7% regression in service_worker.service_worker_micro_benchmark at 421600:421630

Project Member Reported by nhiroki@chromium.org, Sep 29 2016

Issue description

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

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


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

android-nexus5X
Components: Blink>ServiceWorker
Cc: nhiroki@chromium.org
 Issue 651618  has been merged into this issue.
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 29 2016

Cc: robliao@chromium.org
Owner: robliao@chromium.org

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

Hi robliao@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Remove Extra Underscore
Author  : robliao
Commit description:
  
BUG=649363, 650705

Review-Url: https://codereview.chromium.org/2378153002
Cr-Commit-Position: refs/heads/master@{#421611}
Commit  : 420af6678ef6a2cff2e34abf62f3b5b0cc83ee7a
Date    : Wed Sep 28 19:51:29 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@421599  179.741  1.9814   5  good
chromium@421607  179.453  2.39665  5  good
chromium@421609  177.119  3.10594  5  good
chromium@421610  179.156  3.11607  5  good
chromium@421611  233.764  1.85462  5  bad    <--
chromium@421615  232.474  4.9309   5  bad
chromium@421630  229.452  6.0748   5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 651619

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests service_worker.service_worker_micro_benchmark
Test Metric: concurrent_100_response_50_percentile/concurrent_100_response_50_percentile
Relative Change: 27.66%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/709
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000145154517719520


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

| 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!
Status: WontFix (was: Assigned)
Most of these graphs are the restoration of actual performance stats due to
https://codereview.chromium.org/2358723002
Cr-Commit-Position: refs/heads/master@{#420118}

Having said that
ChromiumPerf/android-nexus5X/service_worker.service_worker_micro_benchmark / concurrent_10_response_90_percentile

looks like it may actually be a real regression somewhere.

Sign in to add a comment