Weird RR machine distribution.

[juan carlos echeverry]

Greetings.

We have 27 machines, some more powerful than others..... we use RR in a daily basis, but we have found out that many times, when you submit a job to the farm, the software distributes the job between most of the machines, but just at the beginning..... after some time, the powerful machines stop rendering, and the rendering gets only done by the weak ones.... one or two weak ones, being ALL the machines available..... that creates a bottleneck as the last 5 or 7 frames of a given project can last much more than all the rest. We have tried manually assigning the job to the idle machines but it doesnt work..... its sad having 27 nodes and watching a job been made by only 2 or 3... (and not the best machines). I dont know what we have to do to achieve an even distribution of the jobs. 

If you can enlighten us , we would be very grateful. 

Thank you in advance.

[RR, Schoenberger]

Hi

 

 

 

>. We have tried manually assigning the job to the idle machines

Please take a look at the frame bar in rrControl after you submitted a job.

It shows you what’s happening.
It displays if all frames have already been send to clients for rendering (blue) or if there are some available frames (white):

If there are no available frames any more, then the only option to re-distribute them is to Abort (without disable) the job.

 

 

 

 

It seems that your Sequence Divide min setting is too high.

e.g. if you have 100 frames and the min would be set to 10, then the job can be send at max 10 times.

And if a client got these 10 frames, it finishes these frames.

 

Then there is a setting in rrConfig to adjust how many frames will be send to a client.

Note that it only adjusts the number of frames within the Sequence Divide min/max.

A second influence on the calculation how many frames are send within that range is the machines Processor Speed (PS), the faster the more frames.
The third parameter is that a client should render at least 3 minutes.

 

 

 

If you want to know why a client does not take a job:

Please select the job and the client in rrControl.
Then execute menu Debug/Show "Send job to client?" decision (Why is a job send/not send?).

You can copy the dialog text with hotkey CTRL-C and paste into this ticket.

 

 

 

regards,
Holger Schönberger

Craftsman and Keeper of the Royal Render Flame

Please use the rrKnights Tavern
or our support system for new questions.

[juan carlos echeverry]

Thanks, we will try this and let you know.

--
If you reply, the message is send to the user group which is sufficient and desired.
("Reply All" might send the message twice to the last author which is not required.
Replying "in private" prevents other users to see the answers and might not be seen by the single receiver if he has email rules in place.
If you want to talk to us in private, please use support (at) RoyalRender instead)
---
You received this message because you are subscribed to a topic in the Google Groups "Royal Render Knights Tavern" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rrKnights/oXHiIQyda3o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rrKnights+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rrKnights/001f01dc642c%24a4cba3a0%24ee62eae0%24%40RoyalRender.de.

--

[Diego Zuelli]

I can relate. It happens to us all the time. And I understand the rationale of the algorithm,

There should be an exception that says something like: "when the most powerful machines are free, abort the renders after the current frames, and redistribute the remaining to all the machines according to PS" 

That's a manual task that I should not have to do almost every time...

Thanks!

[RR, Schoenberger]

Hi

 

What are your default Sequence Divide Min/Max Settings?

And what is your setting in rrConfig for the Sequence Divide Mode?