Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: Juraj on 2016-09-27, 02:37:55

Title: [feedback] Distributed rendering precomupation single-threaded only
Post by: Juraj on 2016-09-27, 02:37:55

I've noticed for some time my slaves are super slow to kick-up, which is odd given they're all dual-xeon monsters. It can't be the scene given it starts in seconds on master workstation.

Monitoring task manager showed me the whole precomputation is happening in single-thread only, i.e transforming vertices, parsing the scene and seemingly also large part of secondary GI ?

Is this intended behavior or some bug along the path.

Title: Re: Distributed rendering precomupation single-threaded only
Post by: Juraj on 2016-09-27, 02:44:57

Also, the slaves keep rendering the initial pass over and over. The passes do stack up on master-node, but is the resulting quality identical to if the slaves keep sending more refined result ?
Or is this affected by the time period over which updates are sent ?

Title: Re: Distributed rendering precomupation single-threaded only
Post by: maru on 2016-09-27, 16:23:50

As to #1 - I am not really sure, but I don't see any reason why it should be single-threaded. Ondra should have the final word. You are not using any string options, right?

As to #2 - You got it right. It just resets after the data is sent. So it is by design.
https://coronarenderer.freshdesk.com/support/solutions/articles/12000015664

Title: Re: Distributed rendering precomupation single-threaded only
Post by: Juraj on 2016-09-27, 18:05:38

I don't even use that feature. Every node ( 1.4.1 corona, both public and daily), exhibit this. Will try to make screenshot.

Title: Re: Distributed rendering precomupation single-threaded only
Post by: Juraj on 2016-09-27, 20:07:46

Can any big DR user chime in on his experience ?

Title: Re: Distributed rendering precomupation single-threaded only
Post by: mraw on 2016-09-27, 21:11:03

I'm not rendering very heavy scenes, so for me it's not that a big difference.
Transforming vertices seems to be single-threaded- yes. But not secondary GI- what do you mean 'large parts' of it?
Maybe my secGi-calculation is too short and I don't see it switching from single to multi-threading.
I'm using 1.3

Title: Re: Distributed rendering precomupation single-threaded only
Post by: Juraj on 2016-09-28, 12:25:53

Transforming takes the longest, but parsing is the second after. These two together, take almost 5-10 minutes, opposed to 20 seconds on master pc. My scenes are around 1GB big. (although they can have a slew of proxies and xrefs attached so that true, virtual size could be almost 2GB).

Title: Re: Distributed rendering precomupation single-threaded only
Post by: Juraj on 2016-10-03, 13:20:21

Is the any chance we'll see new DR in 1.5 release ? I've seen around here that at least 3dsMax will be pre-launched.

Title: Re: Distributed rendering precomupation single-threaded only
Post by: Ondra on 2016-10-03, 13:45:29

it wont make it into the release, sorry. We will try to release it ASAP in 1.6 daily builds  though

Title: Re: Distributed rendering precomupation single-threaded only
Post by: sevecek on 2017-04-04, 18:27:18

Is this issue resolved in the new DR? I'm not seeing a big difference in parsing times on slaves.

Title: Re: Distributed rendering precomupation single-threaded only
Post by: Juraj on 2017-04-04, 18:57:08

Quote from: sevecek on 2017-04-04, 18:27:18

Is this issue resolved in the new DR? I'm not seeing a big difference in parsing times on slaves.

I will check tonight. But I think it's quite some time ( recent dailies ) that this is indeed fast now.

Title: Re: [feedback] Distributed rendering precomupation single-threaded only
Post by: Ondra on 2017-04-07, 16:24:48

hi, is this confirmed as resolved?

Title: Re: [feedback] Distributed rendering precomupation single-threaded only
Post by: Ondra on 2017-04-10, 11:29:14

no longer happening