Issue metadata
Sign in to add a comment
|
14%-19.3% regression in v8.runtimestats.browsing_desktop_classic at 460433:460578 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982970963858867408
,
Apr 7 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_retina_perf_bisect Benchmark : v8.runtimestats.browsing_desktop_classic Metric : v8-gc-incremental-step_sum/browse_search/browse_search_google_india Revision Result N chromium@460432 56.134 +- 8.12044 21 good chromium@460578 56.442 +- 5.38538 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.runtimestats.browsing_desktop_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982970963858867408 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6350178530885632 | 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!
,
Jul 20 2017
,
Aug 22 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mlippautz@google.com
, Apr 7 2017