New issue
Advanced search Search tips

Issue 707695 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

30.9% regression in v8.runtimestats.browsing_mobile_classic at 460219:460274

Project Member Reported by ulan@google.com, Apr 3 2017

Issue description

See the link to graphs below.
 

Comment 1 by ulan@google.com, Apr 3 2017

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

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


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

android-one

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : v8-gc-full-mark-compactor_max/browse_news/browse_news_reddit

Revision             Result                  N
chromium@460218      74.2641 +- 43.1365      21      good
chromium@460274      73.8204 +- 37.3864      21      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 --story-filter=browse.news.reddit v8.runtimestats.browsing_mobile_classic

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

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


| 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 u...@chromium.org, May 12 2017

Labels: Performance-Sheriff-V8
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 21 2017

Labels: Hotlist-Google
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jul 24 2017


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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : v8-gc-latency-mark-compactor_max/browse_news/browse_news_qq

Revision             Result                  N
chromium@460258      9.16688 +- 2.06095      16      good
chromium@460335      9.34871 +- 2.93307      14      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 --story-filter=browse.news.qq v8.runtimestats.browsing_mobile_classic

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973171302068003984


For feedback, file a bug with component Speed>Bisection

Comment 8 by u...@chromium.org, Jul 25 2017

Status: WontFix (was: Assigned)
Perf bot cannot reproduce the regression.

Sign in to add a comment