Thanks fiontarWould it be too much to ask you to render a baseline one core, one thread run?

Second, I had heard about this 'when I'm thru with my sector I just stand idle' approach. This is unfortunate! In my renders, it is almost always one sector that holds up the entire thing, namely the head of a/the character with reflect in the eyes, dynamic hair and often hair casting shadows. Sometimes the head/hair only consumes 10% of the frame, but requires 60% or more of the render time. Hell, sometimes 80% of the render time. Even with four sectors, you know that fate will put that head in only one sector just to torment me.

Also, your advice is smart about quitting each time you and coming back in for a fair comparison. Additionally, there is another consideration, the opposite. Do one render and throw away, then do the timed render. That way, resources that are common to the scene stay loaded (texture maps!) and the tests do not count the loading into the comparison.

This last approach would be from the mindset of the animator. If we are rendering 500 frames, the load-up on the first frame is 'an investment' that does not have to be made subsequently. 

Sad to hear that rendering the shadow map is single thread/core. For animation, it needs to be calculated for every frame. I'd have loved to have heard all four cores attack this. (note: there are strategies with animation for not rerendering shadows, multi pass, background in post, etc.)

Fiontar, i'm not asking you to change your testing method...we can still see the comparison your way. Thanks for doing the testing.

::::: Opera :::::