New issue
Advanced search Search tips

Issue 781197 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 780202
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.5%-300.6% regression in v8.browsing_desktop at 512433:512453

Project Member Reported by mlippautz@google.com, Nov 3 2017

Issue description

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

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


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

chromium-rel-mac12
chromium-rel-win7-gpu-intel

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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : total:500ms_window:renderer_eqt:v8_max/browse_search/browse_search_google_india

Revision             Result                  N
chromium@512433      147.73 +- 222.85        21      good
chromium@512453      125.344 +- 273.431      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.search.google.india v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection
Cc: -mlippautz@google.com mlippautz@chromium.org
Mergedinto: 780202
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Zhenyao Mo
  Commit : 77604d4d295b16c91b935c0a3e035a574532a497
  Date   : Mon Oct 30 03:22:48 2017
  Subject: Call UpdateGPUInfo and UpdateGpuFeatureInfo always on GPU process launch.

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max/browse_media/browse_media_flickr_infinite_scroll
  Change       : 4.77% | 58568704.0 -> 61364906.6667

Revision             Result                   N
chromium@512425      58568704 +- 1048576      6      good
chromium@512431      58219179 +- 605396       6      good
chromium@512434      58830848 +- 2431023      6      good
chromium@512435      61364907 +- 1210791      6      bad       <--
chromium@512436      61539669 +- 2052996      6      bad
chromium@512437      61452288 +- 642119       6      bad
chromium@512448      61277525 +- 478607       6      bad
chromium@512470      61364907 +- 3451286      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.flickr.infinite.scroll v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

=== 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_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : total:500ms_window:renderer_eqt:v8_max/browse_search/browse_search_google_india
  Change       : 131.28% | 61.7194861736 -> 151.836739583

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/2b2a41840dfeb57f521e7638b3c05c663f0ba7d9..61377e588b14bbc07c9aef458cd2b413da6f079a


Revision             Result                  N
chromium@512413      61.7195 +- 121.215      9        good
chromium@512421      52.4975 +- 59.7705      6        good
chromium@512425      56.8913 +- 106.684      14       good
chromium@512426      51.2057 +- 80.5405      9        good
chromium@512427      ---                     ---      build failure
chromium@512428      139.246 +- 150.057      9        bad
chromium@512429      144.761 +- 236.901      14       bad
chromium@512444      126.267 +- 219.862      14       bad
chromium@512475      151.837 +- 116.028      9        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.search.google.india v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment