Issue metadata
Sign in to add a comment
|
17.9% regression in blink_perf.parser at 384639:384656 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 4 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : WTF::ThreadSpecific should use base::ThreadLocalStorage. Author : esprehn Commit description: Let's use the base abstraction to allocate the TLS. It's way less code. Review URL: https://codereview.chromium.org/1849023002 Cr-Commit-Position: refs/heads/master@{#384650} Commit : 56641fdb889c6b5d27997465b622d7432c0ba0b8 Date : Fri Apr 01 19:01:26 2016 ===== TESTED REVISIONS ===== Revision Mean Value Std. Dev. Num Values Good? chromium@384638 12046.51243 198.25748 5 good chromium@384647 12257.45145361.309252 4 good chromium@384649 12073.680938137.32303 4 good chromium@384650 10128.33592 92.151066 5 bad <- chromium@384652 10224.92168341.998518 5 bad chromium@384656 10042.645162166.82626 5 bad Bisect job ran on: linux_perf_bisect Bug ID: 600263 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests blink_perf.parser Test Metric: innerHTML-setter-siblings/innerHTML-setter-siblings Relative Change: 16.63% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6367 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016325907996224080 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=600263 | 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 Tests>AutoBisect. Thank you! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by toyoshim@chromium.org
, Apr 4 2016