I'd also appreciate that a lot if you'd implement this feature to work per profile!
Currently I have my Dell XPS 15 9560 with i7 7700HQ and GTX 1050. This machine is so hot that it requires at least two different performance profiles.
- The first one is the most CPU efficient and doesn't care about GPU at all. This is needed for the max CPU performance.
- The second one I'd like to turn on automatically when the GPU hits 64 C. The thing is that with that profile I'd like to make as much room for the GPU as possible.
It'd all gone good until I realized that I can't bind my speed shift range limits from the TPL window to a profile.
Idk if there is another way to accomplish what I need. I have tested that I can't just set Power Limits as this way I've got some very noticeable freezes (whatever, Power Limits are also in the TPL window and can't be set per profile), so the best choice for me would be to limit the clocks via Speed Shift for such a profile. This work perfectly fine for my needs. The last choice (I haven't tested yet as it seems won't work) is to use the old way of Clock Mudulation per profile. But I'm not sure if that's going to help me much as I'm trying to avoid extra heat if possible from the CPU at a cost of its performance (and if I understand it correctly Clock modulation is going to just pollute processor tacts with garbage instructions (like nop) which is anyway going to make some additional heat (in comparison to the Speed Shift). I'm going to test this too anyway as it seems that there is no choice for me other than that. If you know something that can help me with that I'd appreciate!
BTW,
unclewebb, is ThrottleStop available somewhere as open source? It'd be very cool if such an app could be open source so that community could develop and support it.
UPDATE 1.
I've just quickly tested Clock Modulation and it's what I've expected:
- Speed Shifting from 3.6Ghz to 2.1 Ghz reduces power from 43 Watts to 21.5 Watts.
- Clock Modulation from 3.6 Ghz to ~2.1 Ghz (56.25% modulation) reduces power from 43 Watts to only 29.5 Watts.
Really wish this feature as it seems to be very effective (will save me 8 Watts! that is almost 20% of what I can afford with my heat sink).
Everybody, let's upvote this feature. Every vote matters!
UPDATE 2.
Also, I'd like to share my tests if someone is interested in my approach of fighting this ugly
power limits on Dell XPS 15 9560.
For some reason (I haven't spent much time on that) my GPU works really strangely, it seems that power limit depends on the temperature (but what exactly???) but with some kind of a delay: when I run FurMark and burn the GPU at max possible speed (also run CPU intensive jobs at the same time) it allows to grow the temperature to 77 C and then I see this
power limit notification and the clocks drops from 1833 Mhz to 700 Mhz (seems to me like some kind of very aggressive cooling policy applies) but if I reduce the CPU clocks with Speed Shift to 2.1Ghz max and run the same FurMark (this time without any additional payload as in the previous one) but try to avoid fast temperature growing, it shows
power limit notification on 66 C and already drops some Mhz but not so drastically - still tries to preserve good performance.
Of course FurMark isn't a practical example! Let's try some more real world things. I've tested this CPU clocks reduction with Speed Shift in The Witcher 3: Wild Hunt. When I run without CPU clocks reduction (which in the game gives me 25 Watts of CPU), GPU immediately throttles from 1830 Mhz to 1300 Mhz which drops from 37 FPS to somewhere around 29 FPS (the precision of FPS doesn't matter here as we try to avoid throttling). When I run with CPU clock reduction to 2.1Ghz (which in the game gives me only 13 Watts of CPU!) I don't experience any throttling (to be honest, I've also cut max GPU frequency from 1830Mhz to 1630Mhz as these 200 Mhz eat too much and give too less) and the GPU is loaded on 100%. The GPU and CPU temperatures are 64 C (instead of 80 C).
Conclusion. I suppose it's very much in demand for laptop users to have TPL window settings per profile.
UPDATE 3.
I think there is a workaround (a little bit ugly but still going to work) to this problem with profiles (some coding required): I'm not sure if we can use command-line arguments to supply for TS to tweak some settings (that would simplify the work) but it's definetly not a big deal to write some app-crutch that will monitor GPU temperature, once conditions are met it stops TS, replaces ThrottleStop.ini for another preconfigured (so we will have one ThrottleStop.ini per profile this way) and starts ThrottleStop back again.
But I'd hope for the support of the feature inside the TS to not write such crutches
