New issue
Advanced search Search tips

Issue 746263 link

Starred by 1 user
Status: Duplicate
Merged: issue 742808
Owner: ----
Closed: Jul 2017
Cc:
mlippautz@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

61.1%-81.7% regression in v8.runtimestats.browsing_desktop at 485662:485785

Project Member Reported by mlippautz@chromium.org, Jul 19 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 19 2017 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=756dedee1ec7f6eb2759905da35ca3fc63078ec72093a20b253a89a34918051d


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

chromium-rel-win7-dual
chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 19 2017 


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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_sum/browse_social/browse_social_twitter_infinite_scroll

Revision             Result                 N
chromium@485661      137.639 +- 204.99      21      good
chromium@485709      151.027 +- 185.1       21      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.social.twitter.infinite.scroll v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jul 25 2017

Mergedinto: 742808
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Alexander Timin
  Commit : 214a2f9dd64151cfb5626020d8ba74f2d72012a2
  Date   : Wed Jul 12 01:19:03 2017
  Subject: [scheduler] Refactor renderer scheduler policies.

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_sum/browse_tech/browse_tech_discourse_infinite_scroll
  Change       : 69.76% | 8.89314285714 -> 15.0972142857

Revision             Result                  N
chromium@485660      8.89314 +- 13.3473      14      good
chromium@485734      10.2957 +- 18.4408      14      good
chromium@485755      11.7316 +- 24.4262      21      good
chromium@485757      8.75489 +- 12.8346      9       good
chromium@485759      12.2126 +- 19.6088      14      good
chromium@485760      22.5203 +- 43.2561      14      bad       <--
chromium@485764      23.582 +- 36.8592       14      bad
chromium@485773      20.9183 +- 34.4585      14      bad
chromium@485810      15.0972 +- 27.0564      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.tech.discourse.infinite.scroll v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment