Android-Enhancer
Android-Enhancer copied to clipboard
iamlooper
Suggestion of more efficient and practical VM/Virtual Memory Tweaks than the current ones (Sorry for this being an issue)
Hello, I came to recommend adjustments that could be more beneficial than the ones you currently use.
First, VM parameters: echo "80" > /proc/sys/vm/swappiness echo "80" > /proc/sys/vm/vfs_cache_pressure
Reasons for these two:
With vfs_cache_pressure at 80, this would be beneficial to minimize the latency of three aspects of the system: CPU, MEM and I/O.
The reason? Well, more "reusable" data will be in RAM memory, this eliminates the latency required by the CPU to search for data in storage, because they are arranged and ready in RAM.
This also eliminates I/O competition, allowing I/O to be distributed more evenly for the game, because less storage will be used by the CPU, after all, there will already be data in memory for this.
This generally eliminates the latency acquired by the CPU, RAM and I/O.
In the case of RAM, it is because it sends less data to ZRAM, which, in addition to speeding up processes, also eliminates some of the latency of information exchange between RAM and ZRAM.
Furthermore, the value 80 is much more efficient, safe and stable than that used in modules like YAKT (which uses 50), because it does not put extreme pressure on RAM (which prevents memory from being consumed unnecessarily + the CPU from searching for more data than necessary, minimizing the "back seek" latency).
Reason for swappiness at 80: as seen by Ktweak on XDA, keeping more data in RAM reduces data exchange latency.
This works in synergy with vfs_cache_pressure, because both "work in a similar way"
with vfs allowing reusable data to be kept in more RAM, and swappiness preventing this data from being sent to ZRAM.
This overall eliminates data exchange latency by up to 10%.
An example: in Minecraft, I had drops of up to 49fps, with the minimum being 53
With these two adjustments, I was able to make the drops to 53, with the minimum being 56.
This is a significant improvement in stability because it is more "efficient in reusing cache + keeping them in RAM".
I do not recommend reducing these parameters more than recommended, because this can break the "synergy" that I mentioned before.
