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

Issue 755082 link

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



Sign in to add a comment

30.6% regression in v8.browsing_desktop at 492509:492602

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

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

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

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


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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-total_max/browse_social/browse_social_twitter

Revision             Result                 N
chromium@492508      7.3459 +- 3.29386      21      good
chromium@492602      7.4351 +- 3.70696      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.social.twitter 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/8971300463430621408


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 15 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: ae70b0de54a76aa638f9680263ac774fe13c48f2
  bad_revision : 537e04ed985bb235d2b333cfebfdfdef9e7a80ef

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-total_max/browse_social/browse_social_twitter

Revision             Result                   N
chromium@492405      6.447 +- 1.73099         6      good
chromium@493199      7.7075 +- 1.97215        6      good
chromium@493299      6.706 +- 2.60079         9      good
chromium@493349      6.50617 +- 1.14536       6      good
chromium@493362      6.24567 +- 0.408611      6      good
chromium@493368      6.45683 +- 1.27648       6      good
chromium@493371      9.73283 +- 1.6328        6      bad
chromium@493374      9.39667 +- 1.48799       6      bad
chromium@493398      9.15633 +- 1.38136       6      bad
chromium@493596      9.2205 +- 1.42958        6      bad
chromium@493992      9.42367 +- 1.81667       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.social.twitter 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/8971282929702303104


For feedback, file a bug with component Speed>Bisection

Comment 6 by petermarshall@chromium.org, Aug 16 2017

Mergedinto: 755089
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment