POV-Ray : Newsgroups : povray.beta-test : Code gets the processor too hot? : Re: Code gets the processor too hot? Server Time
17 May 2024 18:55:14 EDT (-0400)
  Re: Code gets the processor too hot?  
From: Ger
Date: 2 Apr 2013 13:24:51
Message: <515b1463$1@news.povray.org>
scott wrote:

>>> The simpler your scene is, the less memory it takes as a whole, and
>>> therefore the more of it can be kept in the CPU caches; as a result, the
>>> CPU spends more time doing actual work than waiting for main memory
>>> operations to complete.
>>
>> Shouldn't matter here because in both cases the object data is the same.
> 
> I don't think the object data is the same, in one case you have a
> difference object with N+1 child objects, in the other one you have N
> nested difference objects, each with 2 objects.

True, as clipka pointed out to me.

> 
> My suspicion is the nested objects cause a lot more "memory" type work
> for the processor during rendering (reading pointers, transform data
> etc) and as such even though the CPU is at "100%" it's having an easy
> time waiting for slow memory operations to complete.
> 
> How do the CPU temperatures vary as you change the number of particles -
> are they much closer with just 1 or 2 particles?

Don't know yet, but I'll try and test it a little later today.

-- 
Ger


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.