Tweet
Rendering animations per DR can be a problem, if the rendering of a frame is be done within a short time, for example 15s, but starting of the DR need approx. 15 s - so not much time can be saved. (Extrem example, some times DR helps a little, but not so much like expected.)
So, my idea is, that the user starts several Rhino tasks with the animated scene at the master machine, but each Rhino task is using only a part of the slaves only. The image output directory of Bongo is set to the same location. Bongo has a great little feature - if a frame rendering is started a placeholder file is saved at the output directory first. So, other tasks doesn't start this frame too and start the next needed frame. At this way the DR startup delay would be run parallel at the Rhino tasks.
In my case I have 4 slave machines and if each Rhino task with one slave would need 30s (15s+15s), than per multi-task-setup I could get 8 frames per minute instead 2..3 frames/min only. In my example I could half the render time.
Additional it could be useful to limit the processor cores of the master machine to the rhino tasks. In my case I have 8 cores at the master machine. Per task manager I could set 2 cores for each Rhino task. In this case, if a light cache pass is used, than I would limit it to 2 "num. phases". More phases would not speed up the rendering, filtering and merging need more time for more phases.
So far my thoughts about speed up an animation rendering. My last rendered animation was rendered over night at my master machine, so that I don't tested the multi-task-setup yet. I hope my idea isn't nonsense.
Ciao,
Micha
So, my idea is, that the user starts several Rhino tasks with the animated scene at the master machine, but each Rhino task is using only a part of the slaves only. The image output directory of Bongo is set to the same location. Bongo has a great little feature - if a frame rendering is started a placeholder file is saved at the output directory first. So, other tasks doesn't start this frame too and start the next needed frame. At this way the DR startup delay would be run parallel at the Rhino tasks.
In my case I have 4 slave machines and if each Rhino task with one slave would need 30s (15s+15s), than per multi-task-setup I could get 8 frames per minute instead 2..3 frames/min only. In my example I could half the render time.
Additional it could be useful to limit the processor cores of the master machine to the rhino tasks. In my case I have 8 cores at the master machine. Per task manager I could set 2 cores for each Rhino task. In this case, if a light cache pass is used, than I would limit it to 2 "num. phases". More phases would not speed up the rendering, filtering and merging need more time for more phases.
So far my thoughts about speed up an animation rendering. My last rendered animation was rendered over night at my master machine, so that I don't tested the multi-task-setup yet. I hope my idea isn't nonsense.
Ciao,
Micha
