[Galaxy S III Android Development] MaxI9300:
How can you know that ? Sorry but i'm not soo expert...

I 'm curious to try 400/100 to force the system to use compulsory the z ram .... Can't figure out if the rom will have benefit

---------- Post added at 08:07 PM ---------- Previous post was at 07:51 PM ----------

For those one who wants to test this rom with zram various setting, hete is a little explenation on how it works (from Lord Boeffla site, thank you!)

Expected impact: Improve multitasking by adding virtual zram

zRam is a concept to tackle the limited internal memory (like 1GB only in the Galaxy S3 I9300) by compressing parts of it.

Technically, zRam is an area in the devices memory that is defined to be compressed. This memory area will be used to create a swap device in it. In the end, this adds to your overall memory and with average compression rates of around 35%, can help significantly to overcome the limits.

Note: This has nothing to do with usual swap where the swap device is located on storage! So it does not put any wear on your storage, means, it will NOT be dangerous for your device at all!

By switching this option to on, one or multiple zRam devices will be created with the configured total size (see below) and activated.

zRam is fully dynamic, this means not used parts of the zRam do not consume any physical memory.

Note: If you switch this option off again, it can take up to several minutes to unload everything from zRam and put it either back to normal memory or dump it. Please be patient and wait until the dialog in the app disappears again.

7.8 Number of zRam devices

Default: maximum supported by kernel

Expected impact: Multipe zRam devices can improve overall zRam performance

Original zRam implementations always used one single zRam device, however it seems spreading this to a number of zRam devices improves the overall performance as multiple CPU cores can balance this work out when they are anyway activated. This becomes especially apparent when you are using heavy games that require lots of memory, as during games all CPU cores are assumed to be active anyways.

For normal daily usage, a single zRam device might be perfectly fitting your needs, however there is nothing wrong to have multiple devices always. For gaming persons, multiple devices are reported to help significantly.

Note: You can only change this setting if you switched zRam to Off before.

7.9 zRam total disk size

Default: 100 MB

Expected impact: Define total size of zRam used

This value defines how many MB of physical ram should be reserved to be used for zRam. zRam is fully dynamic, this means not used parts of the zRam do not consume any physical memory.

This size is the total size for zRam, so if you configured multiple zRam devices, this total size is automatically be divided by the number of devices and activated accordingly.

Example: you configured to use 4 zRam devices and set the total size to 600 - this will result automatically in 4 zRam devices with 150 MB each.

In fact, proven good values for the total size are something around 300-600, but also 100 or 200 can also help already when you have memory issues.

You can try which size fits you best, there is no harm in playing with this setting.

Note: You can only change this setting if you switched zRam to Off before.

7.10 Swappiness overwrite

Default: Off

Expected impact: Control how zRam is used - memory handling / smoothness

Linux swappiness is the rate at which a Linux kernel moves pages into and out of active memory.

In our case, zRam uses swap partitions in a compressed memory area. So the swappiness parameter determines how aggressively zRam will be used by the system.

60 is the stock kernel setting without any swap. If you activate zRam in Boeffla-Kernel, the swappiness will be set to 80 automatically.

However, by enabling this switch you can overwrite with your own rate. You can set it to higher values like 90 or 95, which many report to use zRam even more efficiently for them. Others set it down to 30 and are more happy. It depends on your memory requirements and usage pattern.