SOD doesn't happen on Franco, luckily because my phone is sensitive for it
Sent from my Galaxy Nexus using Tapatalk 2
The final winner tunables are running perfectly stable here on the GNex of my wife and on my own GNex.
No problems with 192/1228
I used a lot of gaming, listening to music, web browsing with Chrome, Tapatalk and Repligo Reader (PDFs). Performance and battery life are just amazing, no stability issues at all.
This is for the N7 but a similar test was done for the GN a few months back:
The GN results were similar. IO speed increases to a point with higher read_ahead_kb buffer values, then decreases again.
If I recall correctly, 2048 was found to be the sweet spot both times.
Edit: Wrong graph.. I'll try and find the one with 3072, etc.
Here we go, it's from M-Kernel, but results are similar:
Most people I've seen comment say that 95/85 is slightly laggier than 90/80, so I'm with Fen, I'd like to see if we can tell the difference with:
Hmm.. but you're right, maybe lowering the timer_rate to 15 allows us to use 95/85... okay, so:
Benchmarks are one thing, real usage is another one.
With 2048 i feel my phone being sluggish in transitions. The best way to test that is scrolling the widget section very fast. Its simple a no go for me.
After that i tested some other values, and for now i found that 256 gives me the best transition in the Widget Section.
I didn't know exactly which comment to quote since there have been dozens on comments with different tunables but why the just from 30 to 15? I haven't seen anything in between like 20 and 25. We might as well get it perfect instead of just dividing the numbers in half each time for a test, I've seen every other number be tested in increments of "5" except this one.
Franco believes that by setting the timer_rate to be the same thing as the CPU sample_rate (which is preset at 30000), then that will make the CPU more efficient at switching
|4.0.4, 4.1, 4.2, best kernel, best support, fast, franco, galaxy, jb 4.1, kernel, nexus, samsung|