Issue metadata
Sign in to add a comment
|
12.2% regression in media.tough_video_cases at 381082:381107 |
||||||||||||||||||
Issue descriptionLets see what the bisect says
,
Mar 29 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : base: Implement GetCurrentThreadPriority. Author : erikchen Commit description: The Chrome thread priority is saved in the thread dictionary during SetCurrentThreadPriority(). This seemed a better approach than using thread_policy_get(), since there are 4 Chrome priorities which won't cleanly map to thread flavors. BUG=554651 Review URL: https://codereview.chromium.org/1620673003 Cr-Commit-Position: refs/heads/master@{#381102} Commit : 42655dd168d884f60c0194e8a74606c68a3e6378 Date : Mon Mar 14 22:55:13 2016 ===== TESTED REVISIONS ===== Revision Mean Value Std. Dev. Num Values Good? chromium@381081 488.4 11.081516 5 good chromium@381096 483.4 13.049904 5 good chromium@381099 490.0 8.124038 5 good chromium@381101 485.2 11.344602 5 good chromium@381102 529.8 11.75585 5 bad <- chromium@381107 527.6 12.581733 5 bad Bisect job ran on: mac_10_10_perf_bisect Bug ID: 598431 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests media.tough_video_cases Test Metric: idle_wakeups_browser/idle_wakeups_browser Relative Change: 8.03% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2068 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016909703214004640 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=598431 | 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 chcunningham@chromium.org
, Mar 28 2016