Building a Distributed Rendering Farm

What We're Building

A production-ready distributed rendering farm that automatically provisions Clore.ai GPUs, distributes Blender rendering jobs across multiple nodes, and achieves massive parallelization for complex 3D scenes and animations.

Key Features:

  • Automatic multi-GPU provisioning via Clore.ai API

  • Frame-based job distribution across render nodes

  • Support for Cycles GPU rendering (CUDA/OptiX)

  • Real-time progress monitoring

  • Automatic frame collection and video assembly

  • Cost-optimized spot instance usage

  • Fault tolerance with automatic re-rendering of failed frames

Prerequisites

  • Clore.ai account with API key (get one herearrow-up-right)

  • Python 3.10+

  • Blender project files (.blend)

  • Basic understanding of 3D rendering

Architecture Overview

Step 1: Clore.ai Render Farm Client

Step 2: Blender Render Engine

Step 3: Distributed Job Coordinator

Full Script: Production Render Farm

Cost Comparison

Setup
250 Frames (1080p)
Time
Cost

Clore.ai (3x RTX 4090)

250 frames

~20 min

$0.50

Clore.ai (5x RTX 3090)

250 frames

~25 min

$0.40

Single RTX 4090 (local)

250 frames

~60 min

~$0.15 (power)

AWS p4d.24xlarge (8x A100)

250 frames

~15 min

$8.00

Render farm (commercial)

250 frames

~30 min

$10-50

Performance Tips

  1. Use OptiX for RTX cards (faster than CUDA for ray tracing)

  2. Match GPU to scene complexity — simple scenes don't need A100

  3. Distribute evenly by GPU power, not node count

  4. Use spot instances for batch rendering (50%+ savings)

  5. Pre-bake lighting and physics before distributed render

  6. Use persistent data to avoid re-uploading textures

Next Steps

Last updated

Was this helpful?