Nah i run 1.4-1.5 on both, what do you recommend for best battery life / performance?
Well, I recommend that you NOT run both cores at the same time all the time. You shouldn't need them both on at the same time for 95% of your daily use. Look at your voltage settings in Kernel Tuner. I assume that these voltages are for EACH core...someone please correct me if I am wrong.
My default settings show 875 mV for 384 MHz. Now double that if you want both cores on at the same time. Now look at the voltage needed at 1512 MHz. It's 1250 mV...now double that...this is a lot of voltage needed to run both cores at max.
For me, the best compromise between performance and battery is to tweak the MPDecision settings. By default, I feel that they're a bit conservative. I'd rather have the second core kick in for a few seconds during certain activities. To make sure it kicks in faster, I've lowered the delay times and the threshold. However, I've also raised the threshold for cutting off the second core so it shuts down sooner.
My aim is to have the second core kick in for a few seconds to help get past any lag I may experience, and then turn right back off. I mostly want to avoid song skips and pauses during graphically intense screen changes. The default MPDecision settings didn't give me what I wanted, so I played around with them. I am still tweaking them, but this is where I am at now.
Service Start Delay Default: 500ms Tweak: 150ms
Threshold Up Load Default: 35% Tweak: 30%
Threshold Up Time Default: 250ms Tweak:150ms
Threshold Down Load Default: 5% Tweak: 10%
Threshold Down Time Default: 250ms Tweak: Didn't change
So I am basically making the MPDecision "decision process" start sooner by 350ms. I've lowered the load to 30% and the time for that load has also been lowered. Since I am using it more for burst speed, I've told it to shut off the second core sooner, by increasing the cutoff to 10%.
In the end, I feel this is a pretty good balance of performance and power. I use Interactive governors for both cores. However, I am still tweaking. One of my performance benchmarks is to play music, and then start doing stuff with the screen. I like to load up the accu-weather animation in the Sense ROMs (full screen) while music is playing...then I open and close the status bar over and over until the music starts to get flaky. The numbers above provide consistent music output for me. I don't mind having more processor than I need, as long as it's limited to bursting.
One thing I haven't even touched on is the scheduler. I have decided to use noop for now. But I have some questions about schedulers, and once I do a search and find a thread on that topic, I'll ask some questions in that thread.
Unless you want your phone to melt.
