The fifteenth point release of RenderPal V2 brings a highly advanced peer-to-peer based system for project files caching. Traditional render farms can severely suffer from large amounts of network traffic arising from project files that need to be loaded from a remote file server for each and every chunk of a job. As network bandwidth is a limited resource, this ultimately leads to increased overall rendering times, often wasting many hours just for loading these files.
With this new release, RenderPal V2 can counteract this problem by caching project files locally on the clients before rendering. Instead of using files located on a remote server, the clients will use locally cached copies of the project files. This means that the files only have to be transferred once per jobinstead of once per chunk, resulting in a tremendous reduction of network traffic. This can decrease overall rendering times by up to 40% and more.
This new version also brings various other general improvements and fixes. Below you'll find a brief description of what is new in this version; release notes and the complete changelog can be found at the bottom of this post.
Peer-to-Peer based Project Files Caching
Project files can now be efficiently cached on clients before rendering which greatly decreases the arising network traffic, leading to reduced overall rendering times.
Option to limit the number of parallel renderings on a client
It is now possible to set an upper limit of parallel renderings that can be executed on a client.
Email notifications now work properly for Gmail and many other providers.
RenderPal V2 got a new all-shiny icon!
Numerous other improvements and fixes
Many other improvements and fixes made it into this new version of RenderPal V2, like the event log tab showing the number of unread events, fixed output filters in the console client and a few smaller renderer updates.
This is only an excerpt of what is new in this release; be sure to read the full release notes: