@thewinterdojer said in How to determine how much over_voltage is needed? [Overclock]:
It almost doesn't seem like it's worth increasing your thresholds through overclocking without enabling performance mode...
That's just from my experience with Ondemand and limited testing. When a game is idle (under the hood) it will downclock to I think it's 600Mhz then kick back up when needed so games on that threshold or even when they need just a small "kick" over the idle clock speed for even a moment it has to clock up and down. I think like TMNT pointed out if you like how it's working I wouldn't worry to much about using Ondemand vs Peformance.
The performance gain on many games might be small but the trade-off if only marginal is worth it to me. Even if the Pi went the way of a singe-o-matic puff of smoke after 6 months. That hasn't been the case though. Instead of guessing where a few extra Mhz of speed might be needed/beneficial I figure juice them all as the electric bill will still only be a few pennies more. I think our rate here is .07 per kilowatt and the Pi is so modestly priced that it has paid for itself month after month of gaming. We usually spend quite a bit more for one evening out vs the cost of one Pi.
I was messing with Soul Caliber which doesn't really work on the Pi at all but you could see the effects of the up/down clocking. The tearing and stuttering would go from awful to horrendous. Lot's of yo-yoing! I was running a small script that shows the speed, temp, etc. and then used watch cgu_temp on a separate monitor to see it kicking up and down. The thought is you can find games that kind of give you an idea how that setting works and how you want to leverage it.
I have to enabled it through the runcommand menu on a emulator by emulator basis correct?
I would imagine you could enable it for just the emulators you want to boost. I set it globally via RetroPie Setup right in ES.
RetroPie Setup
C Configuration / Tools
825 runcommand - The 'runcommand' launch script - needed for launching the emulators from the frontend
5 CPU configuration
6 Force performance