New issue
Advanced search Search tips

Issue 735002 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

86.4% regression in v8.runtimestats.browsing_mobile at 480454:480474

Project Member Reported by mvstanton@google.com, Jun 20 2017

Issue description

Rather severe...
 
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jun 21 2017


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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@480453      9.09943 +- 10.4794      21      good
chromium@480474      9.82676 +- 9.43096      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter v8.runtimestats.browsing_mobile

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

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


| 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 4 by 42576172...@developer.gserviceaccount.com, Jun 21 2017


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_social/browse_social_twitter
  Change       : 33.76% | 8.83142857143 -> 10.7951428571

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4b85b7662b82050ff5c4715fc99e1b7f3355acb1..94eda8d07770b09bee347826714b4b517278cfa2


Revision             Result                  N
chromium@480453      8.83143 +- 8.11945      14       good
chromium@480465      8.40857 +- 10.119       21       good
chromium@480467      9.15986 +- 7.81782      14       good
chromium@480468      ---                     ---      build failure
chromium@480469      10.7709 +- 6.43895      14       bad
chromium@480474      10.7951 +- 8.10747      14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter v8.runtimestats.browsing_mobile

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

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


| 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 5 by sheriffbot@chromium.org, Jul 12 2017

Labels: Hotlist-Google
Status: WontFix (was: Assigned)

Sign in to add a comment