Dolphin, the GameCube and Wii emulator - Forums

Full Version: The Quest to Disable Thermal Throttling
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4
(05-29-2017, 10:50 AM)cruise871 Wrote: [ -> ]My device without any thermal software enabled never gets above 39.5 C for the battery , 42 C for the CPU and 55 C for the GPU.

What device is that? Most modern SoCs *idle* higher than that. I suspect your sensors are lying to you.

(05-29-2017, 11:18 AM)nonexist Wrote: [ -> ]Can you share a build for test?

Sure: http://s2.jonnyh.net/pub/dolphin-5.0-3952-dirty-sustainedperformancemode.apk (no idea if that's the 'correct' build settings though, I think the java code is in debug mode, but the native is still optimised?)
Not sure if it'll be useful, or even work. It's up to vendors to decide how to implement it, and I don't know how to check it's "working" outside of using systrace or something to check the peak clocks. Maybe you'll visually be able to see it's running slower at initial start? But hopefully running the "same" speed 10 minutes later?

(05-29-2017, 06:13 PM)degasus Wrote: [ -> ]Benchmarks usually test two parts: Peak performance within a minute, and battery life on "max utilization". So some device already start to throttle after a minute regardless of the thermal, just to fullify the second test. Bad luck, no benchmark checks the battery efficientcy, eg how many frames in total can be rendered.

Yeah, that ends up encouraging vendors to have a boost mode that lasts *Exactly* the same length of time as benchmarks, then immediately clock down into "battery saving" mode.
Dolphin is detected as normal app and not like a game. For that reason lost priority and then start to lag very shortly
(05-30-2017, 12:53 AM)JonnyH Wrote: [ -> ]Not sure if it'll be useful, or even work.

It works on Pixel O dev preview 2, I'll post more details soon
(05-30-2017, 12:53 AM)JonnyH Wrote: [ -> ]What device is that? Most modern SoCs *idle* higher than that. I suspect your sensors are lying to you.

Xiaomi Mi Mix 

Temperatures received using Kernal Auditor 

Below are the highest temps received on my Letv Max Snapdragon 810 device also at around 2 hours gaming

CPU 84 C
GPU 72 C
Battery 46 C

I wouldn't recommend doing this with a Snapdragon 810 device but 820 and up seem to produce less heat without thermal throttling
(05-30-2017, 07:19 AM)cruise871 Wrote: [ -> ]Xiaomi Mi Mix 

Temperatures received using Kernal Auditor 

Below are the highest temps received on my Letv Max Snapdragon 810 device also at around 2 hours gaming

CPU 84 C
GPU 72 C
Battery 46 C

I wouldn't recommend doing this with a Snapdragon 810 device but 820 and up seem to produce less heat without thermal throttling

You won't be able to sustain that anyways, the S810 consumes an absolutely silly amount of power in just the CPU alone (in some case double what other similarly species chips need).
JonnyH
Here's a video comparison without/with sustained mode (sustained mode starts 1:30m)
Looks good as an optional feature /hacks?.
Additionally it'll be great to include VR mode to, it should get +200MHz boost

Sustained performance mode:
All CPUs are capped to ~1.2GHz
GPU frequency is capped to 315MHz

VR mode:
All CPUs are locked to ~1.44GHz
GPU frequency is locked to 510MHz
GPU BUS min_freq is raised to 790MHz
(05-30-2017, 08:25 AM)zxcvbad Wrote: [ -> ]Additionally it'll be great to include VR mode to, it should get +200MHz boost

It might be interesting, but only if it can run like that indefinitely. Otherwise we'll be in exactly the same position with throttling again.

I had a quick glance, and it didn't seem 'trivial' to propogate a setting into the Java wrapper for the emulation activity, though that may be because I know rather little about android app programming. I will try to have a look soon ish, but if someone else has the time feels like giving it a go don't let me stop you.

Also it should probably be wrapped in one of the appcompat classes, as dropping support for anything older than N sounds like it might annoy some people.
Well, termal throtlling appears when CPU reaches a dangerous temperature, disabling it may overheat the CPU even more and then. Bye Bye Smartphone Smile
It's not a good idea to let your CPU go over 90 °C
Working perfectly here to. The for test build.
(05-30-2017, 08:20 PM)EblfIYH Wrote: [ -> ]Well, termal throtlling appears when CPU reaches a dangerous temperature, disabling it may overheat the CPU even more and then. Bye Bye Smartphone Smile
It's not a good idea to let your CPU go over 90 °C


I don't think anyone here is seriously proposing "disabling" the throttling as such, as that's insane, so much as trying to figure out the best way of getting long-term performance - if that can avoid bouncing between a 'boost' and 'slow' mode as it overheats then cools and instead can sit at some level between the two that'll be a better user experience.

It should also me less 'misleading' to users, if they run the app for a little while and *think* that'll be the expected performance going forward.
Pages: 1 2 3 4