Stina & The Wolf, a project by Portmouth University students, is an impressive example of this, beginning life as a personal project for director Paul Charisse.
But when the scale of the story blossomed, he and Alex Counsell (principal technician at the School of Creative Technologies, University of Portsmouth) began developing it as a vehicle for the creation of an in-house studio where students could gain exposure to real-world challenges, techniques and a full production pipeline.
When looking for an industry-proven render management system the team approached PipelineFX. PipelineFX, well experienced with education thanks to the use of Qube! in around 200 schools already, gave the team and sent an engineer down to Portsmouth to help set up the initial 50-node render farm.
Watch Stina and the Wolf here and in check out PipelineFX's own Josh Bretag' top tips on how to stay on top of the game...
01. Render using your workstations
Today's desktops are powerful multicore machines with enough RAM to operate as great render nodes as well as workstations. Many jobs can be running in the background even while an artist or student is working.
02. Run multiple jobs
Run more than one job per host where possible. Learning how to maximise your farm through multiple jobs per host can vastly increase productivity. Use cases include running lightweight 2D jobs (requiring IO) on machines running heavy 3D renders (requiring CPU).
03. Automate the process
Improve your success rate with automation. Automate as many processes as possible. Automatically retrying failed frames, forcing retries to a different host and auto-wrangling bad jobs and machines all improve the chances of success for your render queue.
04. Invest in storage
Ensure your pipeline has the throughput required to handle the load from your render farm and workstations accessing information simultaneously to prevent system overload. Look at increasing the storage I/O. A smart render manager will overwhelm underspecified storage systems.
05. Create subnet groups
Keep your network subnets small. This is commonly overlooked and is something that can cause huge issues as a site grows. Create smaller subnet groups of render nodes and workstations below 32 hosts, and always have your server infrastructure in a separate subnet.
Next page: five more top render management tips
Thank you for reading 5 articles this month* Join now for unlimited access
