v2 daily builds - offline rendering faster than DR

[maru]

The problem is that I did not do my tests properly (I did not check daily build local vs daily build DR). Maybe denisgo22 made some mistake, like having two different versions installed on the computers?
I will redo the tests ASAP and post the results here.

Sorry for the extra confusion. :)

[TomG]

Just a quick test - this was just coincidence, I was using DR to speed up making an image for the website, and noticed this.

So, same scene, set to render for 80 passes, using latest V2 daily (Jan 8th). When the render completes, here is the reported noise level:

No DR: 6.11%
DR : 20.4%

The DR was quicker (and this is a small image, with small number of passes, so DR really didn't have time to kick in), but the take away here is that the noise limit is reporting different if DR is used vs not, even if passes is used as the render limit. The noise in the images seems the same to me, so it isn't that the noise is different, just how it is being reported.

This does mean if you render to noise limit, DR images will "take longer" as they are in fact rendering to a much cleaner version of the image - as you can see if I want "6% noise" then my DR cut off would have to be set to 20% noise or so, due to the number being reported wrong.

[mike288]

Thanks for testing. It is fixed and the fix will be most probably in next daily. Track the changelog for that ...

[TomG]

Cheers Mike :)

[maru]

Tests from the newest daily build. It seems to work pretty much as expected, but I still have one question - why with DR it reported 38 passes rendered, even though pass limit was set to 30? Is it because some extra passes were sent from the node after the rendering was stopped on the master?

(30pass = pass limit set to 30)
(noise7 = noise limit set to 7)

[TomG]

That would be the cause as far as I know - the pass limit is based on the passes that the local machine has, so I believe two things can happen
1) Local machine has 29 passes, does the 30th itself, and asks the nodes for their last updates, which will add more passes and take it over 30
2) Local machine has 29 passes, and a node says "Here! Have another 6 passes!" which takes it over the 30 (plus, it will then collect any additional passes from any other nodes)

From my thinking, this will be affected by how long a pass takes to render in combination with how often the nodes send updates (fast rendering passes with longer update times, then increased chance of nodes adding a greater number of passes over the limit; longer passes and faster updates from the nodes, more likely they will just add one or two extra passes)

[mike288]

Yes exactly - master gathers all remaining passes from slaves (since they are already done) which may exceed the set limit. It just further improves the result.

[Ondra]

yep, we dont want to discard passes just so we dont overrun the limit ;)