Create a video rendering farm using DIY methods.
Create a video rendering farm using DIY methods.
I explored options for combining your identical i5 desktops to share a video rendering workload. Since direct networking wasn't feasible, I considered creating a virtualized Windows PC that would aggregate all the cores. The i5 models are VPROs, so I’m unsure if this approach would work without further guidance.
You have options, though it varies by editing tool. You might need a separate program that supports rendering across multiple devices on a network. For example, Premiere Pro doesn’t natively use render farms. The best approach I can offer is to install Adobe Media Encoder or another suitable software for rendering video projects on each machine. Keep your primary workstation for editing and send the final file to any connected computers for rendering. I’ve only configured render farms for 3Ds Max before.
The idea of merging all PCs into a single unit isn’t feasible, especially when Windows treats them as one system with 48 cores. Instead, for rendering tasks, you should run an instance locally on each machine. The software will split the workload and distribute parts to each device, but combining all CPUs seamlessly isn’t possible. This is mainly due to the limitations of current networking speeds—typically around 1 Gbps Ethernet—which is much slower than the internal bandwidth between CPU, RAM, and other processors.
I recommend searching for information online and reviewing conversations similar to the ones on Adobe forums.
It used to be a viable option, but it’s no longer practical. Render farming can support 3D tasks for animations and games, yet modern setups render much slower on farms than locally. It would essentially consume excessive time, energy, and cooling resources. (Note: Explanation added) Recent improvements in video rendering have shortened what once took hours or days to minutes. Even a 30-minute session on modest hardware is reasonable. But the delays from splitting jobs, moving huge data volumes over slow connections, and re-rendering often make it inefficient overall.