Swarm is much smarter on how it communicates over the network. Older Distributed Rendering Interface in V-Ray for Maya You also needed to make sure that every DR machine was using the exact same version of V-Ray. Additionally, you would have to know how much power each DR machine had and if it was up to the task at hand.
Some of the limitations of this old system is that you had to know the port and all the addresses of the DR machines. When going to render, you would need to select which computers you want to use, and then render. Additionally, you would need to know the port used for DR. Then from the computer you are launching DR you need to know the network address (usually the IP) of every computer you want to use. Then you would have to launch a Spawner program that would listen over the network if it had any tasks to do. In order to use DR, V-Ray had to be installed on every machine that you needed to render on. Through the local network, it gets all the data that it needs to render a bucket, calculates it, sends that bucket back, and moves on to the next task. Distributed rendering takes it a step further and adds more cores by talking to other computers on the network. As each bucket is done, it moves on to the next one that is not being worked on by another core. The simplest way is by rendering small portions of the image, known as buckets. Render engines like V-Ray take advantage of this by distributing those tasks among the many cores (GPU or CPU) on your computer. The general idea is that renderings can be broken up into many little tasks. It has been a part of V-Ray since version 1. Distributed rendering (DR) is nothing new.
0 kommentar(er)
