Back to InsightsCloud & VDI

Building High-Throughput Hybrid VFX Pipelines: Bridging Local NVMe to AWS

How to scale rendering to AWS while keeping your artist workstations responsive on-premise. We examine 100GbE local NVMe cache clusters, intelligent S3 asset synchronization, and hybrid burst orchestration.

DZ
Derek ZavadaFounder & Principal VFX Systems Architect
Jan 28, 20259 min read293 views
#AWS#Hybrid Cloud#Storage#NVMe#Networking#100GbE#ZFS

The Hybrid Dilemma in Modern Visual Effects

Studios are constantly caught between two competing realities:

  1. On-Premise Latency Advantage: High-end comp and 3D lighting artists require sub-millisecond file access to scrub uncompressed 4K and 8K EXR sequences in real time.
  2. Cloud Scalability: When delivery crunch hits, an on-premise farm of 30 nodes cannot finish 500 shots overnight. You need 2,000 cores on AWS for 8 hours without bankrupting the project or choking the studio's internet uplink.

The solution is not choosing one or the other — it is architecting an intelligent Hybrid Data & Compute Pipeline.


Anatomy of a Zero-Bottleneck Hybrid Architecture

A production-grade hybrid setup separates data into three distinct tiers:

text
[ Artist Workstations (Rocky Linux / Mac) ]
       │ 100GbE Fiber Switch
       ▼
[ Tier 1: Local High-Speed NVMe Storage Cluster (TrueNAS / ZFS Cache) ]
       │ Continuous Hash-Based Differential Sync (AWS DataSync / S3 Express One Zone)
       ▼
[ Tier 2: Amazon S3 Production Asset Repository ]
       │ High-Bandwidth Cloud Fabric
       ▼
[ Tier 3: AWS Deadline Cloud Dynamic Spot Render Fleet ]

Step 1: Solving the Asset Synchronization Problem

The biggest pitfall in cloud rendering is uploading entire asset libraries repeatedly. If every render job pushes 40GB of textures and geometry over WAN, your pipe saturates and renders sit queued for hours.

To solve this, we implement Content-Addressable Asset Caching:

  • Assets are broken down by SHA-256 hash.
  • Before submitting a Deadline Cloud job, the submission plugin computes local file hashes and queries S3.
  • Only missing or modified chunks are uploaded to the queue's S3 bucket.
  • Render workers cache downloaded assets on local ephemeral NVMe instance store volumes (e.g. c6id or g5 instances), ensuring subsequent tasks execute immediately.

Step 2: Optimizing Network Fabrics (100GbE on Prem)

On the local side, 10GbE is no longer sufficient for multi-artist 4K multi-layer EXR playback. We design storage fabrics using:

  • Dual-port 25GbE / 100GbE Mellanox ConnectX NICs with RoCEv2 (RDMA over Converged Ethernet).
  • ZFS pool topologies with dedicated NVMe mirror vdevs for metadata and small blocks.
  • Jumbo frames (MTU 9000) configured across all switches to eliminate packet fragmentation.

Summary: Results from the Field

By deploying this hybrid architecture:

  • Local artists enjoy steady 1,800 MB/s sequential read rates in Nuke and DaVinci Resolve.
  • Overnight deliveries scale across hundreds of AWS EC2 Spot instances automatically.
  • Total cloud data transfer costs drop by up to 65% through deduplicated asset staging.
DZ

Derek Zavada

VFX Pipeline TD and Systems Engineer specializing in AWS Deadline Cloud, high-throughput cloud rendering, Linux studio infrastructure, and custom pipeline workflows for Nuke, Maya, Blender, and Flow Production Tracking.

Related Insights & Architecture

AWS Deadline Cloud

AWS Deadline Cloud Shared Job Bundles: Simple, Scalable, & Powerful

How shared job bundles revolutionize render management in AWS Deadline Cloud. Eliminate template duplication, empower artists with self-service queues, and manage OpenJobDescription (OJD) archives seamlessly via S3 and the Deadline Cloud CLI.

Building High-Throughput Hybrid VFX Pipelines: Bridging Local NVMe to AWS | DownZero