Appropriate ZRAM size for XZP? - Sony Xperia XZ Premium Questions & Answers

I'm experiencing extensive app lag/kill/reload when using XZP (with A12 ROM) as my daily driver recently.
Then an app called DevInfo tells me that 2047MB of 3075MB of RAM on my phone is for ZRAM, and it's always full.
So my question is, is using over half of the RAM as ZRAM good or bad for the phone's performance?
Thanks in advance.

Update:
The app name is DevCheck.
I found a Magisk module which is able to change ZRAM size.
Its GitHub page is here:
https://github.com/yc9559/qti-mem-opt
I'm going to test different ZRAM size with it.

Related

[Q] RAM Manager? (edit: Heap size)

I recently had a couple of issues with an app called "TouchDraw". The problem was that, on occasion, the app would fail to load certain images because of low memory, and would insert placeholders instead.
This happened even though I have over a gig of free RAM available.
So I contacted the app developer, to see if it was a bug or something, but it turns out (according to them anyway) that android by default only allows apps to use up to a maximum of like 256mb of RAM, no matter how much RAM is actually available. They also said there was nothing they could do about this from their end, and the only way round it was to root.
Fortunately, I have my Note rooted already, so:
Is there a universally recommended RAM management app that I should be using? I have looked and found a few, but I'm unsure on the differences. A lot of them were reviewed based on phones and difference uses... Seemed safer to ask first.
Thanks!
Edit: actually it turns out its the heap size I need to change. Seems there is a tool called "vm heap tool" that does this... But only on older devices with small heap sizes. Need to find an alternative!
any recommendations?
Minfree manager
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Minfree manager
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Hmm... from what I can see, all that does is close down programs quicker so that I have more free RAM?
I have plenty of free ram, its just that android limits the amount of memory that an app can use. Apparently theres a way around this if you are rooted?
Unless I'm misunderstanding something.
Edit: Plus, minfree seems to be designed for phones? The help/guides I can find for it all seem to deal in tiny amounts of ram (relative to the 2gigs I have)
Edit 2: Hmm, it would seem that I need to increase my heap size... the line "android:largeHeap = true" keeps coming up when I search for the answer to this question. I will have to investigate further!
Edit 3: seems that value is for app debs only perhaps. There was a tool that did what I needed to the default heap values (vm heap tool) but it only supports much smaller heap sizes. Will have to look for an alternative!
nirurin said:
Hmm... from what I can see, all that does is close down programs quicker so that I have more free RAM?
I have plenty of free ram, its just that android limits the amount of memory that an app can use. Apparently theres a way around this if you are rooted?
Unless I'm misunderstanding something.
Edit: Plus, minfree seems to be designed for phones? The help/guides I can find for it all seem to deal in tiny amounts of ram (relative to the 2gigs I have)
Edit 2: Hmm, it would seem that I need to increase my heap size... the line "android:largeHeap = true" keeps coming up when I search for the answer to this question. I will have to investigate further!
Edit 3: seems that value is for app debs only perhaps. There was a tool that did what I needed to the default heap values (vm heap tool) but it only supports much smaller heap sizes. Will have to look for an alternative!
Click to expand...
Click to collapse
Edit 4: Well turns out I managed to do it.. I think. I modified my build.prop, and changed my heap from 256mb to 320mb. Seems to have done the trick! At least, this app hasnt had any more ram issues since.
heap size gt-8020
nirurin said:
Edit 4: Well turns out I managed to do it.. I think. I modified my build.prop, and changed my heap from 256mb to 320mb. Seems to have done the trick! At least, this app hasnt had any more ram issues since.
Click to expand...
Click to collapse
I am noob to android, I have heap size 265mb on galaxy note 10.1, gt-8020, android 4.1.2. not rooted.
I need for photo mate r2 application heap size of minimum 512mb to be able to save edited raw photos to jpg without that application is useless, developer say that heap size is problem and indeed with smaller files (editing) saving is working
can somebody please point to recent root procedure and how to edit my build.prop and change my heap to 512mb
thanks

[Q] What is ZRAM?

I had a search about and really I am only looking for confirmation as to whether this is accurate or not...
CALIBAN666 said:
I think its better to Post this here,when its not better,than sorry!!!
-----------------------------------------------------------------
Once a brief statement for those who are not traveling so long in the Android scene:
ZRAM = ramzswap = Compcache
In order to explain more precisely ZRAM first need other terms are more clearly defined:
Swap can be compared with the swap file on Windows. If the memory (RAM) to complete the PC the data that are being used not actively outsource (eg background applications) so as to re-evacuate RAM free. To this data is written to a hard disk. If required, this data is then read back from there easily. Even the fastest SSD is slower than the RAM. On Android, there is no swap!
In ZRAM unnecessary storage resources are compressed and then moved to a reserved area in the fixed RAM (ZRAM). So a kind of swap in memory.
This Ram is more free because the data then only about 1/4 of the former storage requirements have. However, the CPU has to work in more because they compress the data has (or unpack again when they are needed). The advantage clearly lies in the speed. Since the swap partition in RAM is much faster than this is a swap partition on a hard drive.
In itself a great thing. But Android does not have a swap partition, and therefore brings Android ZRAM under no performance gain as would be the case with a normal PC.
In normal PC would look like this:
Swap = swap file (on disk) -> Slow
ZRAM (swap in RAM) -> Faster than swap
RAM -> Quick
With Android, there is no swap partition, and therefore brings ZRAM also no performance boost.
The only thing that brings ZRAM is "more" RAM. Compressed by the "enlarged" so to speak of the available memory. That's on devices with little RAM (<256MB) also pretty useful. The S2 has 1GB but the rich, and more than. There must not be artificially pushed up to 1.5 GB.
After you activate the ZRAM also has 2 disadvantages. The encoding and decoding using CPU time, which in turn has higher power consumption.
Roughly one can say (For devices with more than 512MB RAM):
Without ZRAM: + CPU Performance | + Battery | RAM
With ZRAM: CPU Performance |-Battery | + RAM
For devices with too little RAM so it makes perfect sense. But who shoots the S2 already be fully complete RAM and then still need more?
Check whether you can ZRAM runs in the terminal with
free or cat / proc / meminfo
I hope it helps to understand zRam!!!!
Click to expand...
Click to collapse
Taken from here
That looks accurate, but it's a little hard to understand. A basic explanantion of zRAM is that zRAM compresses an actual block of RAM in order to have more RAM available to the system. If you make the compression too high with zRAM then your device will actually go slower as a result. An example of going over the top would be adding 256MB of RAM using zRAM on a phone that only has 768MB RAM (that's almost a 50% compression rate because ~600MB is available to the user). zRAM also requires the CPU to compress and decompress the data.
Zram is not ram. It is a virtual memory, also known as swap space, which lives in the ram. Virtual memory is the part where the system stores memory fragments which are not accessed, making more room for apps to store information in the ram. Most Pcs work with virtual memory on disk, but Linux has a zram feature, aka CompCache, which can hold unused pages in a compressed manner in memory, thus makes more ram available by compressing unaccessed pages.
Sent from my HTC Sensation Z710e using xda premium
so this ZRAM tweak is only useful for devices with low RAM's isn't it? well thanks for the info i dont wanna sacrifice batt life for some unnoticeable effect on my s3
once zram is enabled ....how do u remove the partition completely from.the ram after disabling it?
I noticed that my galaxy s duos comes with zram . However I wish to disable the partition and instead use swap partition in /cache .
So....how do I completely remove the partition space in ram?
Thank you .
Virtual Memory
Raven2k said:
Zram is not ram. It is a virtual memory, also known as swap space, which lives in the ram. Virtual memory is the part where the system stores memory fragments which are not accessed, making more room for apps to store information in the ram. Most Pcs work with virtual memory on disk, but Linux has a zram feature, aka CompCache, which can hold unused pages in a compressed manner in memory, thus makes more ram available by compressing unaccessed pages.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Sorry but you have a wrong concept of "Virtual Memory".
Google "virtual memory wiki" for the full article.
All programs have access only to their own "virtual" memory space of 4GB on 32bit OS'
But internally to the OS, that full virtual address space is divided on pages of 4KB each.
The OS manages all programs pages, if not enought RAM is available, it starts writing pages to the Page File / Swap partition.
When a program tries to read or write from its virtual memory address which page is not on physical memory, the OS launches a Page Fault Exception, takes over execution and reads the faulty page from storage (page file or swap partition) to physical memory, and if necessary writes another page to storage to make room for the requested page. Then it resumes the program execution.
From the article. Android does not have a Swap partition, but it compresses pages to ZRAM.
geno83 said:
Sorry but you have a wrong concept of "Virtual Memory".
Google "virtual memory wiki" for the full article.
All programs have access only to their own "virtual" memory space of 4GB on 32bit OS'
But internally to the OS, that full virtual address space is divided on pages of 4KB each.
The OS manages all programs pages, if not enought RAM is available, it starts writing pages to the Page File / Swap partition.
When a program tries to read or write from its virtual memory address which page is not on physical memory, the OS launches a Page Fault Exception, takes over execution and reads the faulty page from storage (page file or swap partition) to physical memory, and if necessary writes another page to storage to make room for the requested page. Then it resumes the program execution.
From the article. Android does not have a Swap partition, but it compresses pages to ZRAM.
Click to expand...
Click to collapse
True but not completely.
Android doesn't require ZRAM nor swap to work. It is a linux fraction but it doesn't act like linux completely.
Could anybody tell me the best way to improve ram efficiency without sacrificing batt
Thread cleaned. Either post relevant replies or don't post.
Right now, I have a full ZRAM. How does RAM handles it?
Sent from my Moto G4 Plus using XDA Labs

[MOD] Fixing N7's RAM issues

The following are two ram optimising scripts that actually do something. They will ensure a fluid experience by keeping a minimum of 100mb of ram free. Simple as that.
STEPS:
Download zip and extract files "boost" and "freeram".
On the tablet , use a root file manager
Paste files in /system/bin (system needs to be re-writable obviously)
Set permissions to rwxr--r--
Activate scripts manually after every boot using android terminal emulator:
1) free ram (to see ram usage)
2) su
3) freeram (no spaces)
4) boost
5) free ram (to see ram usage - compare to values in step1)
6) Profit
Explanation:
"boost" - activates Adrenaline Boost V3 (i take no credit for this script). What this does is clear the ram cache, freeing up ram storage.
"freeram" - a script i made, adjusts minfree values (android's built in ram manager) to kill off more empty apps from ram when ram usage exceeds certain values - not a task killer, so doesn't affect battery life
In android terminal emulator:
"su"
"cat /sys/module/lowmemorykiller/parameters/minfree"
-will show you the prior minfree values, "freeram" script adjusts these to 8192, 10240, 12288, 21000, 23000, 26000
Notes:
All changes reset on boot, so you'll need to to run everytime you reboot
check your ram usage before with: "free ram"
These two scripts will generally ensure about 300-400mb free ram always.
Removing widgets will improve this also.
If after a while nexus is feeling slow again, run "boost" script.
Fstrim or "lagfix" also helps with those having slow emmc issues
Enjoy more free ram
Or download an app called autokiller memory. Works miracles
mrazndead said:
Or download an app called autokiller memory. Works miracles
Click to expand...
Click to collapse
didn't know about that app.
This is more geeky and cleaner though, who doesn't want to use terminal??
And i don't think the app flushes the ram cache (similar to the adrenaline v3 script)
According to anandtech:
"I’m told that TRIM support has been part of the eMMC standard since around version 4.2, it was just a matter of enabling it in software. The result is that the new Nexus 7 shouldn’t have these aging affects at all. Better yet, fstrim support has also been added to the old Nexus 7 with as of the Android 4.3 update, so if you’ve got a Nexus 7 that feels slow, I/O performance should get better after fstrim runs in the background. I'm checking on whether the other Nexus devices have also had TRIM support added. I would consider the slow storage aging problem fixed as of now, and Google took the eMMC and storage I/O performance issues with the previous Nexus 7 to heart for this version."
Link: http://anandtech.com/show/7176/nexus-7-2013-mini-review/4
So that's good news for poorly ageing nexus 7's, just update to 4.3 instead of running lagfix
@mods: close/move the thread please.
this is another minfree / lowmemkiller script like Supercharger V6 which offers nothing more than actually less memory. What do I mean? It makes the device start killing apps/processes much sooner rendering it multitask-less. Provides a boost but at a terrible cost: much less mem available to apps...
I was able to multitask smoothly between 8 open apps without reloads. And I've been using this setup for 2mths or so.
I had memory issues with my n7, and this solved them, and I wanted to share as users (can't remember the thread name) were discussing slowness due to limited free ram, and this worked for me.
Mods feel free to close, sharing experiences is not appreciated obviously..
mpokwsths said:
@mods: close/move the thread please.
this is another minfree / lowmemkiller script like Supercharger V6 which offers nothing more than actually less memory. What do I mean? It makes the device start killing apps/processes much sooner rendering it multitask-less. Provides a boost but at a terrible cost: much less mem available to apps...
Click to expand...
Click to collapse
So basically, the Xda crowd is too dumb to make up their own minds?
Shouldn't it be up to the individual to try this (and any other) mod freely. Your personal experience with similar mods is welcome, but you trying to tell others what is best for them is way out of line imo.
IceColdJellied One X
Tapatalk 4 Beta
Shared knowledge = more knowledge imho
Thanks for sharing it! :beer:
On linux systems having a little amount of free ram is not necessarily a bad thing. it means that the apps you use most are available to be opened very quickly.
OP: what do you mean by "empty app"?
Appreciate your effort, OP. However, a more user-friendly way is to install an app like Rom Toolbox(and others) and change minfree. RT has presets, and set at boot features. I personally subscribe to the thought process that unused ram is wasted ram.
Nbsss said:
According to anandtech:
"I’m told that TRIM support has been part of the eMMC standard since around version 4.2, it was just a matter of enabling it in software. The result is that the new Nexus 7 shouldn’t have these aging affects at all. Better yet, fstrim support has also been added to the old Nexus 7 with as of the Android 4.3 update, so if you’ve got a Nexus 7 that feels slow, I/O performance should get better after fstrim runs in the background. I'm checking on whether the other Nexus devices have also had TRIM support added. I would consider the slow storage aging problem fixed as of now, and Google took the eMMC and storage I/O performance issues with the previous Nexus 7 to heart for this version."
Link: http://anandtech.com/show/7176/nexus-7-2013-mini-review/4
So that's good news for poorly ageing nexus 7's, just update to 4.3 instead of running lagfix
Click to expand...
Click to collapse
I wish My poorly aging Nexus 7 hasn't improved at all since the 4.3 update. In fact I think it's running even slower. I haven't run lagfix since the update though since I lost root and I'm waiting for Wug's updated toolkit to get it back. (I know I can restore root with other methods but I'm lazy and toolkits just make it easier.)
Aside from the TRIM issue I loved my old Nexus, but 16gb just wasn't enough space anymore and any time I dipped below 4gb of remaining storage it would lag so horribly I'd have to wipe the whole thing and start over if I wanted it to be buttery smooth again, even after using lagfix. Lagfix helped a bit, but it was still crawling compared to a freshly wiped tablet.
I've got a 2013 Nexus 7 on the way though so hopefully what you said about TRIM on the newer model is true and this one won't age as poorly as the original. Even if it does, having an extra 16gb of wiggle room can't hurt.
My thoughts
The most aggressive lvl on the minfree script is 26K ie 26,000*4/1024 = 101mb
Having less than 100mb of ram (ie over 90% ram used) slows down my n7 and its really bad when i have 19-45mb of ram left...
The fact that the script resets on reboot means i can easily compare the difference, for ME it helps and i can't notice an impact on multitasking (and thx for teaching me how to use terminal to check ram usage )
mrazndead said:
Or download an app called autokiller memory. Works miracles
Click to expand...
Click to collapse
Since i use this app my ram is always ok. Thanks so much, really improved a lot

+24 hours battery life + High performance boost and smooth scrolling

Hello XDA S7 users
So I was hoping for a performance change in Oreo but it's just the same nougat.
We have 4 GB ram and we don't need virtual compressed swap partition in RAM. This was useful in Old android days when devices had 1 Gb ram and that stuff, and I wanted to go swapless. I found this by simple Googling. It's a simple, small magisk module that removes the swap partition from RAM making it all available for the applications. Also to make use from Swap as on Linux desktops Swap should be 2X the size of the ram and not compressed as compression takes from the CPU power.. but this is not the case here, it is actually part of the RAM lol, and it's compressed
By installing the module you
- make all RAM available to the user and apps without virtual disks inside RAM
- preserve CPU as all the time the cpu is compressing and decompressing data to and from the Swap partition. Preserving the CPU gives you a performance boost as more CPU cycles are now available for user.
- Preserves battery by using less CPU power.
This was evident when I used it on the latest Oreo leak ERD2 and now my battery lasts +24 hours and the phone is very fuc*** faster. Apps open instantly and multitasking is way better 'comparable to iPhone' . I even increased animation factor as with default value animations were so fast
The module zip in the devs thread, download and flash in Magisk then reboot.
This module was developed by the talented dev @EarlyMon if this helped consider donating to him, check his thread: https://forum.xda-developers.com/apps/magisk/module-swap-torpedo-run-faster-reliably-t3766883
My setup:
Rom: [OREO][SE9][ERCB][01/04/2018] Galaxy S7 Edge - Oreo DevBase
Using the rom's kernel with Magisk 16.0 and Viper4android. Didn't try with Xposed.
My battery usage is attached too.
Is working for nougat?
AndrOmega said:
Is working for nougat?
Click to expand...
Click to collapse
Yes working on nougat.
Zero lag in ui really neat
pingufanpoy said:
Zero lag in ui really neat
Click to expand...
Click to collapse
im on oreo
pingufanpoy said:
im on oreo
Click to expand...
Click to collapse
Try it on oreo.
applied on my Nougat, lets see how much juice I can get, thanks
Superman 2.9 stock settings. After applying the mod phone freezes very often, returns back to life after few seconds. this happens regularly at no apparent time.
On note 8 port,
Causes freezing , FC of Touchwiz, camera wont start up as well.
Tried a different launcher , same problems.
Please post your oreo set up, like rom etc...
Check the post I added my setup.
Following up frpm previous post.
There are definitely issues the longer you use it.
Seems like the more times you restart the heavier the stutter.
Seems like the zram is necessary because it is taxing on the processor.
My home key and power button disabled themselves after about 2 minutes after booting and even booted into download mode by itself until i uninstalled the module.
Too bad for those of you experiencing trouble, I wish it weren't so.
Zram (or Samsung's vnswap) is MORE taxing on the processor, not less.
But the additional swap does allow more bloat to be crowded into ram while swapping out essential functions for fast reloading. (Why anyone would build an Android where essential functions COULD be unloaded escapes me but it is what it is.)
There are no lingering effects to the module and it runs one functional command at startup - nothing extra runs after boot, less runs. The Swap Torpedo isn't a new tactic, just a new method that takes advantage of the systemless modification for startup thanks to Magisk.
Sorry to those that are having problems with it - thanks for trying it, and definitely uninstall it. Life is too short for a broken phone!
Also consider trying it with your next update, rom, or phone. The majority of Samsung user feedback has been overwhelmingly positive.
EarlyMon said:
Too bad for those of you experiencing trouble, I wish it weren't so.
Zram (or Samsung's vnswap) is MORE taxing on the processor, not less.
But the additional swap does allow more bloat to be crowded into ram while swapping out essential functions for fast reloading. (Why anyone would build an Android where essential functions COULD be unloaded escapes me but it is what it is.)
There are no lingering effects to the module and it runs one functional command at startup - nothing extra runs after boot, less runs. The Swap Torpedo isn't a new tactic, just a new method that takes advantage of the systemless modification for startup thanks to Magisk.
Sorry to those that are having problems with it - thanks for trying it, and definitely uninstall it. Life is too short for a broken phone!
Also consider trying it with your next update, rom, or phone. The majority of Samsung user feedback has been overwhelmingly positive.
Click to expand...
Click to collapse
I tried with new S9 rom, it works best when I made internal storage swap, I have totally uncompressed 4 GB ram thanks to your module and 2 GB uncompressed swap on internel flash memory. I still find it a good move and it worked flawlessly with my other HTC phone.
Lol.. Pretty nice tho.. But showing the 4h sot isnt making it incredible.
I get 5h sot on superman 2.9 with normal use (youtube, games, music, texting, snapchat).
I am interested in the non-lag thing. Will try it, thnx man
do u use your phone ?
Does i need the module?
Sorry to disappoint you with my comment:
1st - 24 hours you are getting is probably because you don't use your phone at all ! same usage with a good Kernel should get you 2 days at least.
2nd - Samsung galaxy S7 Edge does not need any Ram management I mean come on it's a 4Go, there is a Ram cleaning tool already included in Device maintenance.
finally - After trying this module all I got was : performance decreased and weird UI behavior.
Do you really want a great battery and performance? go and try Devbase ROM + MoroKernel and you'll thank me later

Can you change ZRAM with root on stock kernel?

Hi all,
With this Xiaomi device SoC source code was never released so only stock kernel can be used. Is it possible to turn on ZRAM and change ZRAM values with it still if I was to gain root?
Many thanks
LaurenceGough said:
Hi all,
With this Xiaomi device SoC source code was never released so only stock kernel can be used. Is it possible to turn on ZRAM and change ZRAM values with it still if I was to gain root?
Many thanks
Click to expand...
Click to collapse
You already have zRAM enabled by default. AFAIK modern Android devices don't use a swap partition (except RAM+ features).
see your zRAM:
Code:
su
cat /proc/swaps
adjust your zRAM:
Code:
su
swapon --help
the size of your zRAM is defined in
/vendor/etc/*fstab*
WoKoschekk said:
You already have zRAM enabled by default. AFAIK modern Android devices don't use a swap partition (except RAM+ features).
see your zRAM:
Code:
su
cat /proc/swaps
adjust your zRAM:
Code:
su
swapon --help
the size of your zRAM is defined in
/vendor/etc/*fstab*
Click to expand...
Click to collapse
Thanks very much, that command is super useful and no amount of Googling I did could find it!
/vendor/etc/*fstab* reports:
"/dev/block/zram0 none swap defaults zramsize=55%"
This sounds like ZRAM should be enabled at 2.2GB.
The problem with this device is the swap partition is reported as always 2252MB, yet even with the "RAM" boost turned on or off the "swap" partition is reported as the exact same size. I suspected based on the really, really poor memory related performance it is disk based SWAP... Anything more than 2-3 simple apps and they reload constantly like they were fully closed when switching apps. All power saving features are turned off.
P.S I am not rooted just yet, I was just trying to see if I could improve my performance as the CPU is quite strong but memory is the issue.
Thanks again
Edit:
I just ran /vendor/etc/*fstab* again after enabling "RAM boost" and restarting, it says it's on in the app switch view (+2GB) but the output is the exact same of this file, I am not sure if this is to be expected or not. Performance is exactly the same so I guess it's just another MIUI bug?
This "SWAP" partition is also not always full usually only 1GB out of the 2GB in use. Checking against a Pixel 7, it's 3GB of ZRAM (reported as SWAP, but of course no RAM boost or SWAP exists on Pixels) it's fully utilized almost always despite having double the physical RAM.
LaurenceGough said:
at 2.2GB
Click to expand...
Click to collapse
LaurenceGough said:
always 2252MB
Click to expand...
Click to collapse
we calculate with base 2!
=> 1024^2 = MiB = 1.048.576 Byte
=> 1.048.576 x 2258 = 2.367.684.608 Byte = 2,2GiB!!
=> 2258MiB = 2,2GiB
There is no partition or used storage for zRAM/swap on your device. Consider that zRAM is compressed with lz4 (=50% compression). So, 1GiB RAM storage needs only 512MiB zRAM storage. The (de)compression is done by the kernel.
zRAM (and also swap) can't boost your system. These partitions are only used for cached data. Before your kernel deletes this data to clear RAM storage it gets compressd and stored in the zRAM area. It's the most useless data.
zRAM is a dynamic partition on your RAM. If RAM only needs 128MiB zRAM then zRAM won't be greater than 128MiB. It never increases to the full available size until it's really needed. If fsrab states "55%" than 55% is the maximum size of zRAM in your RAM and not a persistent size that is always occupied.
Don't change anything regarding to the RAM management as Android is nearly perfect handling thas by itself. You can only make it worse.
Thanks again. The issue I'm facing is that just a few basic apps struggle to run when multitasking, I have disabled all power saving features and MIUI optimisations / powerkeeper daemon but when switching apps or webpages they very often reload fully. I am certain this is an issue with low memory, and I know 4GB is not a lot of memory these days, but I thought I could run more than two tabs in a web browser, and more than a few simple apps without them reloading.
My understanding of zRAM is that it compresses RAM as you say, whilst this taxes the CPU more it should be able to compress more data into the RAM, effectively allowing more apps / webpages (pages) to stay available to use, rather than being killed by the low memory killer dameon lmkd.
Is my understanding correct that this 55% zRAM would provide an extra ~3.3GB or so of compressed RAM, making the total addressable RAM approx ~5.3GB?
If the 2GB of "RAM boost" or SWAP as it should be called if I am correct was working I'd expect it to be able to keep a few more apps or tabs running in memory and prevent a full reload? Is there any way I could check if this is running correctly without root? I know SWAP partitions are not ideal and they have a few downsides but I think this phone has relatively fast storage for its price range.
I am on the lookout for a device with more RAM but it'd be nice to understand a bit more about this situation and learn.
LaurenceGough said:
making the total addressable RAM approx ~5.3GB?
Click to expand...
Click to collapse
Your RAM storage remains 4096MiB. The swapped data in zRAM is compressed and can't processed until it gets decompressed. All data in zRAM actually should have been deleted and this storage isn't acting as additional RAM storage increasing your performance per se.
Apart from that Android's RAM management always uses 60-70% under normal conditions. For peaks, due to some heavy memory using apps, it can increase to 80-90% while at the same time zRAM increases, too. It's correlating. You can't force RAM to swap everthing into zRAM for having 2-3GB available. That's not the meaning of zRAM.

Categories

Resources