{"id":27743,"date":"2014-11-28T09:43:20","date_gmt":"2014-11-28T14:43:20","guid":{"rendered":"http:\/\/www.opensource.im\/?p=27743"},"modified":"2014-11-28T09:43:20","modified_gmt":"2014-11-28T14:43:20","slug":"lollipop-5-0-encryption-causes-bitter-performance-drops","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/lollipop-5-0-encryption-causes-bitter-performance-drops.php","title":{"rendered":"Lollipop 5.0: Encryption causes bitter performance drops"},"content":{"rendered":"<p><p>    Lollipop 5.0 is what Google says to be a    sweet new take on Android, with an abundance of security    features that promise to protect user information from hackers    and snoops. This security, however, may prove to be the hard    candy that may cause a huge amount of strain on the device in    terms of performance.  <\/p>\n<p>    The degree of protection featured in the latest Android OS    works involves an encryption that runs automatically from the    first time a device is turned on. Google sees this as a way to    keep data safer without the need to modify the settings.  <\/p>\n<p>    \"Full device encryption occurs at first boot, using a unique    key that never leaves the device,\" said Google in a blog post.    Sweet, indeed.  <\/p>\n<p>    However, a recent performance test AnandTech ran on two    Lollipop-enabled Nexus 6 devices showed a bitter core beneath    the sugar-coated promise of security.  <\/p>\n<p>    Comparing one with and one without full-disc encryption (FDE)    enabled, the tech publication observed a \"significant    performance penalty that comes with enabling FDE.\"  <\/p>\n<p>    The security feature caused a 62.9 per cent drop in random read    performance, and 50.5 per cent in random write performance.    Meanwhile, sequential read performance recorded a massive 80.7    per cent decrease.  <\/p>\n<p>    Google's move to activate encryption by default is seen to    closely resemble the degree of protection iPhones have recently    provided with iOS 8, where only the lockscreen password can be    used as a key to decrypt. And only the device's owner can gain    access to the user data stored on smartphones or tablets.  <\/p>\n<p>    AnandTech pointed out that eMMC and SoCs used in Android    devices are not equipped to handle FDE without a hit to    performance. That said, users of Lollipop-enabled devices will    have to wait for a while for a version update that fixes FDE's    negative impact on performance.  <\/p>\n<p>    Security vs performance  <\/p>\n<p>    In the light of Lollipop 5.0, the question about data security    in relation to performance becomes all the more urgent.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Excerpt from:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.eetasia.com\/ART_8800707167_499486_NT_d007ad08.HTM\/RK=0\/RS=lfJ67yHK1mnsZ5CuedJWlMuVhEU-\" title=\"Lollipop 5.0: Encryption causes bitter performance drops\">Lollipop 5.0: Encryption causes bitter performance drops<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Lollipop 5.0 is what Google says to be a sweet new take on Android, with an abundance of security features that promise to protect user information from hackers and snoops. This security, however, may prove to be the hard candy that may cause a huge amount of strain on the device in terms of performance. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-27743","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/27743"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=27743"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/27743\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=27743"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=27743"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=27743"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}