C'era il post di Pengus77 a riguardo e linkava al trattato di una esperta di google che brevemente diceva che bloccare della memoria swap limitava la memoria di utilizzo alla fine o qualcosa di simile
qui qualche risposta dell'Ing
Actually it's a bit of a weird thing. See, all unix-based systems are designed to use virtual memory in an efficient way... and they like it a lot. Zram is "the google way". It grabs a small % of your ram and uses it as compressed swap space in memory, effectively reducing your free ram. Pure disk/mmc based swap is "the desktop/server way". But let's consider how it's used... it's not an extension of your ram, it's not used actively to emulate ram, it's used in a sane way to offload the rarely used, or less used - less requested - memory blocks of programs. So basically it's something good to have and in linux world is highly suggested, even if you have tons of ram. Mac OSX for example uses swap/vm files instead of partitions. It's normal for a unix based system to use it, why android should be any different ?I use it in a very aggressive mode... 4 max background processes, disabled zram and ksm, enabled swap on the new bootloader partition, ~30 apps installed (some i don't even use ever, but they're there). DynInteractive or Interactive depending on the task at hand. Row as i/o scheduler. I constantly have ~100Mb free ram available and the system is awesome...