New issue
Advanced search Search tips

Issue 789449 link

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



Sign in to add a comment

45.1% regression in v8.browsing_desktop at 518483:518562

Project Member Reported by jgruber@chromium.org, Nov 29 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 29 2017 

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

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


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

chromium-rel-win7-gpu-intel
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 29 2017 


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_max/browse_media/browse_media_flickr_infinite_scroll

Revision             Result                  N
chromium@518482      4.28167 +- 2.93812      21      good
chromium@518562      4.31695 +- 3.08739      21      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/8961604915032496000


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 30 2017

Mergedinto: 788488
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Mythri Alle
  Commit : 2d88095699f02011d0d0c7d21bf4f348ae453b20
  Date   : Wed Nov 22 11:48:27 2017
  Subject: Remove v8.browsing_desktop and v8.browsing_mobile benchmarks.

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_max/browse_media/browse_media_flickr_infinite_scroll
  Change       : 37.35% | 3.28178571429 -> 4.50755555556

Revision             Result                  N
chromium@518482      3.28179 +- 1.66473      14      good
chromium@518548      3.13011 +- 1.18412      9       good
chromium@518581      3.20356 +- 1.52335      9       good
chromium@518598      3.34643 +- 2.27434      14      good
chromium@518606      3.243 +- 1.45823        14      good
chromium@518608      3.25689 +- 1.51083      9       good
chromium@518609      4.45007 +- 2.79576      14      bad       <--
chromium@518610      4.43733 +- 1.65627      9       bad
chromium@518614      4.50756 +- 2.45226      9       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/8961496228077350960


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

Sign in to add a comment