Issue metadata
Sign in to add a comment
|
36.3%-83.1% regression in blink_perf.layout at 391973:392028 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 9 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : Re-enable complex text path on android Author : eae Commit description: Trying to re-enable the complex text path on Android now that hb_font_t is cached with the user data container instead of the hb_face_t object. This should result in lower memory usage for the complex text code path, we'll watch the memory bots though and revert as needed if it regresses. BUG=577306 R=drott@chromium.org Review-Url: https://codereview.chromium.org/1949053002 Cr-Commit-Position: refs/heads/master@{#392010} Commit : 9af72a88ea5b39c2c36c99f8b091c5feae82ef7d Date : Fri May 06 05:51:07 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@392002 9.7366 0.140172 5 good chromium@392008 9.92969 0.241817 5 good chromium@392009 9.68584 0.16706 5 good chromium@392010 6.15853 0.277337 5 bad <-- chromium@392011 6.25643 0.196452 5 bad chromium@392014 6.36767 0.185785 5 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 610246 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.layout Test Metric: flexbox-lots-of-data/flexbox-lots-of-data Relative Change: 34.60% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1781 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013151350662960400 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5797833102327808 | 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 alexclarke@chromium.org
, May 9 2016