Thanks for the feedback.
Quote:
Originally Posted by kuskro
Let me explain why I chose "seeder (on moderate mode)", it was because it forces the CPU to stick to higher clock frequencies due to the constant I/O using. By default, our iMX6 Cortex is working on CFQ I/O scheduler and PERFORMANCE govenor but it is not enough, so seeder forces the CPU a bit more, despite the fact it uses more battery.
Best.
|
The seeder is only contributing towards the randomization pool. With lot of processes running on the normal smartphones, a case could have been made out for Seeder (even though people seriously question its efficacy). At most Seeder theoretically, would remove the wait of applications waiting for the randomization pool if it ever falls below requirement. It cannot make the CPU go faster. As of now, I have my M96 with OnDemand schedular, which makes it run ~40% at 396 MHz, ~1% at 792 & ~59% at 996MHz. No lag seen. For normal usage, these is no requirement of Seeder. I'm not so sure about heavy usage either. M96 is not a multitasking machine, so any benefit, if perceived might very well be placebo.
Quote:
Originally Posted by kuskro
About what you commented upon windowsmgr.max_events_per_sec=90, it is true that with 90 is enough in common phones but not on our case I think.
|
As per the explanation provided by Jeff in the first link in my previous post:
// This number equates to the refresh rate * 1.5. The rate should be at least
// equal to the screen refresh rate. We increase the rate by 50% to compensate for
// the discontinuity between the actual rate that events come in at (they do
// not necessarily come in constantly and are not handled synchronously).
// Ideally, we would use Display.getRefreshRate(), but as this does not necessarily
// return a sensible result, we use '60' as our default assumed refresh rate.
result = 90;
Any more would just waste resources. I guess we really are splitting hairs here. A value of 90 per second should be more than enough unless we're talking about a harcode GPU capable of some serious gaming. Each one to his own though.
The M96 is supposed to be running at 85Hz screen refresh rate. So 90 still very much covers it.
Quote:
Originally Posted by kuskro
And, about "debug.sf.hw=1", it is set on 1 when you are not sure if compositing is set on 0 by default, that was the case.
|
I've found no difference between enabling it to 1 or commenting it out. So I guess 1 is the default setting. Won't hurt to reapply it though.
I guess performance wise, we're pretty much set. Now we need to channel our energies towards visual aspects, like the point raised by helour above.
Jp