
🎨 3D Rendering & VFX · Network
The network of a VFX studio's render farm: artist workstations, render nodes, high-speed storage and a cloud burst link.
Drawing diagram…
Render farm network topology: artist workstations on a 10 GbE studio network; render nodes (CPU and GPU) on a high-speed 25/100 GbE farm network with a spine switch; shared high-performance storage (NAS/parallel file system) connected to both; the render manager (Deadline) server; and a private cloud interconnect to burst render nodes in the cloud. Internet access only through the firewall.
flowchart TD
subgraph STUDIO["Studio Network 10 GbE"]
WS1[Artist Workstations]
RM[Render Manager Deadline]
end
subgraph FARM["Farm Network 25/100 GbE"]
SPINE[Spine Switch]
CPU[CPU Render Nodes]
GPU[GPU Render Nodes]
end
STOR[("High-performance Storage")]
FW[Firewall]
CLOUD[Cloud Burst Render Nodes]
WS1 --- STOR
RM --- SPINE
SPINE --- CPU
SPINE --- GPU
SPINE --- STOR
WS1 --- RM
SPINE -->|"Private interconnect"| CLOUD
WS1 --- FWWhere each part of a cloud render farm runs: artists' workstations, the render queue manager, autoscaling GPU render nodes and shared storage.
How assets move through a 3D animation or VFX pipeline: modelling, texturing, rigging, animation, lighting, rendering and compositing, with review in between.
A schema for managing 3D assets in a studio: projects, assets, versions, dependencies (textures, rigs), shots and reviews.
The states of a render job on a render farm: submitted, queued, rendering frame by frame, failures and retries, and completion.
How a VFX shot is reviewed: the artist submits a version, the supervisor reviews in dailies, the client approves, and notes flow back.
The studio systems that tie a VFX pipeline together: production tracking, asset management, render farm, storage and client review.