New issue
Advanced search Search tips

Issue 694457 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: 2019-07-09
OS: ----
Pri: 3
Type: Bug-Regression



Sign in to add a comment

28.7% regression in v8.browsing_desktop at 448268:450642

Project Member Reported by ulan@google.com, Feb 21 2017

Issue description

See the link to graphs below.
 

Comment 1 by ulan@google.com, Feb 21 2017

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

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


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

chromium-rel-mac12-mini-8gb
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 22 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: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-scavenger_avg/browse_news/browse_news_reddit
  Change       : 8.59% | 7.61631460583 -> 7.16549900301

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1f2e38edd1f5c21f9c52fb7d718ec87dc9b0b8e1..867223fdd3327e622cb42836fa1ccc2d66465fec


Revision             Result                  N
chromium@448267      7.61631 +- 1.32883      14       good
chromium@449456      7.56005 +- 2.03593      21       good
chromium@450048      7.73182 +- 1.6809       14       good
chromium@450346      7.55942 +- 1.09553      14       good
chromium@450385      7.59968 +- 1.56781      14       good
chromium@450395      7.66993 +- 1.1771       14       good
chromium@450396      7.79079 +- 1.80377      14       good
chromium@450397      ---                     ---      build failure
chromium@450398      ---                     ---      build failure
chromium@450399      ---                     ---      build failure
chromium@450400      7.27884 +- 1.97708      14       bad
chromium@450403      7.11001 +- 1.38952      14       bad
chromium@450421      7.16434 +- 2.09184      21       bad
chromium@450495      7.15144 +- 1.62725      14       bad
chromium@450642      7.1655 +- 1.22747       14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit v8.browsing_desktop

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

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


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

Labels: Hotlist-Google
Labels: Pri-3
NextAction: 2019-07-09
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.

Sign in to add a comment