Quote:
Originally Posted by parousia15
Thanks for the explanation. Is "scaling parameters" something I can alter with setcpu? I have it install, but I have it set to just 998 and 245 ondemnod. I fear overclocking will break my cpu.
I've noticed that on gears, it's a little erratic, it fluctuates between 43-49, which makes it look a little choppy. I think it looked a little more smooth when it was consistently at 31fps.
|
Yes you can, if you go to the advanced tab in setcpu you can change the governor parameters. The 2 you're mainly interested in are sampling rate and threshold.
Sampling rate is how often the governor checks the cpu load to decide if it needs to increase the cpu speed, I personally use 50,000 (about .05 seconds).
Threshold is what % of cpu needs to be hitting before the governor starts increasing the cpu speed, I prefer around 70 to preserve that snappy feeling. Setting it lower can improve performance, but can increase battery drain.
Gears can be a touch misleading to the governor since it doesn't hit the cpu as hard as fps2d might. Generally I tend to advise people to fire up setcpu (or whatever clock control util they prefer) and set the governor to performance for the benchmark to see what your peak is. (Just remember to change it back to ondemand when you're done ofc!)
Quote:
Originally Posted by parousia15
Is that why, the first time around when I run fps2d it works its way up to aboue 54-55 and the sd is larger, while immediately running it a second time, performance is more consistent?
|
That's exactly why.
When you first fire up fps2d, you're probably still running at min, and on that first run the governor will be ramping up the cpu speed to meet the load it's seeing from fps2d.
On the second pass, the speed is already scaled up a bit(unless you let fps2d idle long enough for the governor to scale the speed back down) so there isn't as much fluctuation.