Started by AussiePatriot, October 03, 2014, 05:59:04 AM
Quote from: AussiePatriot on October 14, 2014, 09:11:16 PMI salute you sir,Haven't had a chance to check it yet but I will tonight after work.
Quote from: AussiePatriot on October 19, 2014, 12:01:15 PMSorry for the late reply. I'm typing this from my phone at work. I've had 2 sessions now testing the latest beta. I have configured 2 watchdog rules such as the following:1, when (total) CPU load greater then 64% for 1 second set affinity to 1-3 (I have 4 logical cores)2, when (total) CPU load is greater then 5% for 1 second set afinity to 0-3. The reason I choose 64% is because when core 0 spikes after a reload in-game (splinter cell) the game will hover around 64% total CPU load while I have core 0 spiking. So as you know I simply want core 0 to switch off then back on to make it behave normal again. The first time I tried I only had a quick play around several days ago. It seemed to be applying the rules correctly. But earlier this evening after further testing it will still apply the rules I've created but sporadically. Sometimes the second rule to change afinity back to all cores doesn't kick in after 1 second as I stated, it seems to get confused still. One further thing I'd like to mention is, how difficult would it be to add code to allow the existing watchdog rules to a 'per core' as this would be much more accurate and efficient way to solve this problem by being able to apply these rules to a particular core (in my case core 0)Biiiiiig thx in advance!