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

Issue 632620 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

15.2% regression in service_worker.service_worker_micro_benchmark at 407948:407983

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

Issue description

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

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


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

chromium-rel-mac-retina
Components: Blink>ServiceWorker
Labels: OS-Mac
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jul 29 2016

Cc: jamartin@chromium.org
Owner: jamartin@chromium.org

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

Hi jamartin@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 UMA Precache.Freshness.Prefetch and include validated resources.
Author  : jamartin
Commit description:
  
 - Precache.Freshness.Prefetch measures the freshness (in seconds) of
   all the prefetched resources in seconds since the moment they were
   downloaded.
 - Expose HttpResponseInfo through the call chain of
   UpdatePrecacheMetricsAndState

Precache.Freshness.Prefetch will be useful as a comparison to
Precache.TimeSinceLastPrecache.

BUG=619211

Review-Url: https://codereview.chromium.org/2146023003
Cr-Commit-Position: refs/heads/master@{#407974}
Commit  : 8e1bdb68cb6d13fc258a7498948a3c590929606a
Date    : Tue Jul 26 23:48:22 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N   Good?
chromium@407947  1.035    0.013817   12  good
chromium@407965  1.0325   0.0109752  12  good
chromium@407970  1.03037  0.0145395  27  good
chromium@407972  1.03056  0.011547   27  good
chromium@407973  1.045    0.0436991  27  good
chromium@407974  1.02028  0.0110443  18  bad    <--
chromium@407983  1.01875  0.0106066  8   bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 632620

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests service_worker.service_worker_micro_benchmark
Test Metric: concurrent_1_response_50_percentile/concurrent_1_response_50_percentile
Relative Change: 1.83%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1460
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005820084082260544


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

| 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)
The regression was quite small and the found CL looks harmless.

Sign in to add a comment