New issue
Advanced search Search tips

Issue 757493 link

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



Sign in to add a comment

6.2%-19.9% regression in v8.browsing_desktop at 495707:495808

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 21 2017 

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

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


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

chromium-rel-win7-dual
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 21 2017 


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-finalize_avg/browse_search/browse_search_google

Revision             Result                     N
chromium@495791      0.0935496 +- 0.206584      21      good
chromium@495808      0.0926783 +- 0.177067      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 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/8970632180533834608


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

Comment 7 by 42576172...@developer.gserviceaccount.com, Aug 22 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-full-mark-compactor_avg/browse_search/browse_search_google_india

Revision             Result                   N
chromium@495787      10.6375 +- 0.136472      2      good

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/8970555152028539296


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

Comment 8 by 42576172...@developer.gserviceaccount.com, Aug 22 2017

Mergedinto: 757342
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Nico Weber
  Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6
  Date   : Sat Aug 19 04:23:54 2017
  Subject: win: Turn off clang-by-default again for now.

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-full-mark-compactor_avg/browse_media/browse_media_imgur
  Change       : 12.36% | 48.0893774224 -> 54.0344589415

Revision             Result                   N
chromium@495787      48.0894 +- 1.42938       6      good
chromium@495798      47.7337 +- 3.34703       6      good
chromium@495801      47.2338 +- 2.67017       6      good
chromium@495802      53.2832 +- 1.22294       6      bad       <--
chromium@495803      53.0686 +- 3.1663        6      bad
chromium@495808      54.0345 +- 0.999948      6      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.media.imgur 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/8970555051599276624


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

Comment 9 by 42576172...@developer.gserviceaccount.com, Aug 23 2017 


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

Suspected Commit
  Author : Nico Weber
  Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6
  Date   : Sat Aug 19 04:23:54 2017
  Subject: win: Turn off clang-by-default again for now.

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-full-mark-compactor_avg/browse_search/browse_search_google
  Change       : 33.93% | 11.748 -> 14.4191666667

Revision             Result                  N
chromium@495791      11.748 +- 15.7777       14      good
chromium@495801      14.6893 +- 33.1716      12      good
chromium@495802      15.9567 +- 29.9296      13      bad       <--
chromium@495803      13.5386 +- 24.3941      13      bad
chromium@495805      13.3642 +- 15.5404      14      bad
chromium@495808      14.4192 +- 24.3218      12      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 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/8970555064005642752


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

Sign in to add a comment