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

Issue 607034 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
please use my google.com address
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.5% regression in service_worker.service_worker_micro_benchmark at 389495:389524

Project Member Reported by falken@chromium.org, Apr 27 2016

Issue description

See the link to graphs below.
 

Comment 1 by falken@chromium.org, Apr 27 2016

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

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


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

chromium-rel-win7-dual

Comment 2 by falken@chromium.org, Apr 27 2016

Components: Blink>ServiceWorker
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: roc...@chromium.org
Owner: roc...@chromium.org

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

Hi rockot@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 : Add field trial testing config for MojoChannel
Author  : rockot
Commit description:
  
R=asvitkine@chromium.org
BUG=

Review URL: https://codereview.chromium.org/1918583002

Cr-Commit-Position: refs/heads/master@{#389497}
Commit  : bf36f2d46f43eff11f56ea205615f092801b1004
Date    : Mon Apr 25 16:47:03 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev   N  Good?
chromium@389487  17.718  0.234883  5  good
chromium@389494  18.129  0.250983  5  good
chromium@389496  17.494  0.191488  5  good
chromium@389497  20.115  0.3208    5  bad    <--
chromium@389500  20.145  0.217284  5  bad
chromium@389512  20.285  1.40973   5  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 607034

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_10_response_50_percentile/concurrent_10_response_50_percentile
Relative Change: 14.49%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/679
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9010906101805886928


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

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

Comment 6 by roc...@chromium.org, Jun 27 2016

Status: WontFix (was: Assigned)
This is no longer relevant as the experiment in question is no longer active.

Sign in to add a comment