On 24/05/2018 12:13, William F Pokorny wrote:
> On 05/24/2018 05:25 AM, Stephen wrote:
>> On 23/05/2018 22:07, clipka wrote:
> ...
>>
>> Aside.
>> I run Throttle.exe to monitor my CPU and GPU temperatures. I noticed 
>> that during the rendering of the scene. My CPU was being throttled 
>> back when I was using Ver 3.8 and the tokenizers. I cleaned my fans 
>> and filters last week so I don’t think it is an airflow problem.
>> Has anyone else noticed an increase in temperature with 3.8?
>>
>>
> 
> I've noted nothing with CPU temperature, but I don't routinely watch it. 

For years I ran Pov on a laptop. When your lap starts to burn it makes 
you think. Now it is just a habit.

> Do you see the throttling if you cut back on the number of cores you use?
> 
Looking at the temp graph. I see that one core is running about 5°C 
above the lowest. And yes if I deny that core to Pov then it does not 
throttle. I have set the throttling level at 89°C that is 6°C below the 
CPU shutdown level*. There is a distinct difference between 3.7 and 3.8.

Ach well, it will give me something to do in my free time. Like moving 
the box away from a glass partition.


*
If the internet can be believed. There are a lot of conflicting opinions 
(crap) out there. Obviously no one on the over-clocker forums uses Pov. :)


> What I am seeing in recent work is more volatility in performance 
> measures than has been typical. In the range of -+0.5% run to run of 
> late where I'd been getting <<0.1%. Makes it more difficult to determine 
> whether a local code change has much affected performance. Basically 
> need many more renders or renders with much longer run times.
> 
> Aside: Not talking about parser run times here. I expect those to be 
> more volatile due memory allocations as the scene is digested.
> 

That is a bit above my pay grade. ;)

-- 

Regards
     Stephen

Post a reply to this message