New issue
Advanced search Search tips

Issue 733645 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

140.6%-734.9% regression in blink_perf.shadow_dom at 478929:478990

Project Member Reported by majidvp@chromium.org, Jun 15 2017

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtpW0iwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9sTs8goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1sP2sgoM


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

android-nexus5
android-nexus7v2
android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 16 2017

Owner: hayato@chromium.org

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

Hi hayato@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Hayato Ito
  Commit : 8c1c9878074921a131e9295da6fe0ac003541087
  Date   : Tue Jun 13 10:51:34 2017
  Subject: Use measureTime everywhere in PerformanceTests/ShadowDOM

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : blink_perf.shadow_dom
  Metric       : v1-host-child-append/v1-host-child-append
  Change       : 712.39% | 12.3284625129 -> 100.154666667

Revision             Result                    N
chromium@478928      12.3285 +- 0.0753939      5      good
chromium@478955      11.8975 +- 0.207715       6      good
chromium@478959      11.85 +- 0.298142         6      good
chromium@478960      101.107 +- 2.31687        6      bad       <--
chromium@478961      100.117 +- 4.59256        6      bad
chromium@478962      100.051 +- 3.97115        6      bad
chromium@478969      98.762 +- 1.61895         6      bad
chromium@478982      100.155 +- 4.13484        6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.shadow_dom

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

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


| 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 4 by hayato@chromium.org, Jun 16 2017

Status: WontFix (was: Untriaged)
WONTFIX. This is expected, caused by changing the benchmark itself; measureRunsPerSecond -> measureTime

Sign in to add a comment