New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 713619 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.6%-61.2% regression in v8.browsing_desktop at 461929:462001

Project Member Reported by hpayer@google.com, Apr 20 2017

Issue description

See the link to graphs below.
 

Comment 3 by hpayer@chromium.org, Apr 20 2017

Status: WontFix (was: Assigned)
Recovered.
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Apr 20 2017


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_avg/browse_media/browse_media_pinterest

Revision             Result                    N
chromium@461928      0.329198 +- 0.419003      21      good
chromium@462001      0.334957 +- 0.370407      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.pinterest v8.browsing_desktop

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

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


| 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!
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Apr 20 2017


=== 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: winx64intel_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_avg/browse_media/browse_media_pinterest
  Change       : 5.27% | 0.398505115453 -> 0.377508814668

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/d8ecdc4a0429d984fde83e08a1bb343af2d6851b..e73759e7b2870df901e45294e19bdce9a47a60f6


Revision             Result                     N
chromium@461928      0.398505 +- 0.0593792      14       good
chromium@461946      0.393484 +- 0.107877       21       good
chromium@461955      0.395466 +- 0.13062        21       good
chromium@461958      0.395416 +- 0.106173       21       good
chromium@461962      0.391372 +- 0.0640194      21       good
chromium@461963      ---                        ---      build failure
chromium@461964      0.375272 +- 0.0514497      14       bad
chromium@462001      0.377509 +- 0.0464765      14       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.pinterest v8.browsing_desktop

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

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


| 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!

Sign in to add a comment