Redshift Multi-GPU Rendering in Cinema 4D: How It Scales, VRAM and When More GPUs Pay Off
Redshift renders faster with more GPUs, but only speed is shared, not memory. The main points from Maxon's documentation:
- Speed is shared: All GPUs in a machine can work on the same frame by splitting it into buckets; Maxon notes the gain can be non-linear.
- Memory is not: Maxon support: Redshift does not combine VRAM across GPUs. Four 32 GB cards still mean a 32 GB in-VRAM limit.
- Two modes: Render each frame on all GPUs, or render several frames at once on subsets of GPUs; long, light animations often scale better the second way.
- Measured jobs: On iRender, 150 frames rendered in 1h 42m on 4x RTX 5090 and 360 frames in 1h 18m on 8x RTX 4090 (two different scenes).
- On iRender: 2x, 4x and 8x RTX 5090 or RTX 4090 servers with Cinema 4D and Redshift pre-installed; split long sequences across several servers for deadlines.
Adding GPUs is the fastest way to speed up Redshift, but it does not work the way many people expect. More cards share the work of each frame; they do not add up their memory. This guide explains how Redshift uses several GPUs, what limits scaling, and how to choose between 2, 4 and 8 GPUs, based on Maxon’s documentation and recorded iRender jobs.
Checked against the Cinema 4D and Redshift documentation, November 2026.
1. How does Redshift use multiple GPUs?
Redshift splits each frame into buckets and hands them to the available GPUs, so all cards work on the same frame (Maxon: hardware recommendations). The scene itself is not split: each GPU needs its own copy in its own memory.
How to read the figure. On the left, the frame is shared out bucket by bucket, which is why more GPUs make each frame faster. On the right, each card holds the whole scene, which is why four 32 GB GPUs still give a 32 GB scene limit. Maxon states it directly: Redshift does not combine VRAM when using multiple GPUs (Maxon support).
Two ways to use several GPUs with Redshift
From Maxon's CPU, GPU and hardware recommendations for Redshift.
| Mode | How it works | Best for |
|---|---|---|
| All GPUs on each frame | Redshift splits the frame into buckets and every GPU renders part of it. Maxon notes the gain can be non-linear. | Heavy frames, stills, look-dev and test renders |
| Several frames at once | Separate render processes, each using a subset of the GPUs, render different frames in parallel. | Long animations of light frames where per-frame overhead dominates |
| Several servers | Split the frame range across machines; each renders its own frames. | Deadlines; turnaround drops roughly with the number of servers |
2. Why doesn't Redshift scale perfectly with more GPUs?
Part of every frame is work the GPUs cannot share, and some settings affect how evenly work is spread. Maxon notes that rendering a single frame on all GPUs can give a non-linear gain, and that large buckets can reduce multi-GPU performance unless the image is high resolution (Maxon: System settings).
How to read the figure. Each bar is one frame on 2, 4 and 8 GPUs. The fixed part (scene export, data upload and writing the image) stays the same length, while the shared bucket-rendering part halves each time the GPU count doubles. The fixed part therefore becomes a larger share of the frame, and each extra GPU helps less.
The table lists each limiting factor and what to do about it.
What decides how well Redshift scales
From Maxon documentation; check each factor on your own scene.
| Factor | Why it matters | What to do |
|---|---|---|
| Scene preparation time | Exporting and preparing the scene happens before the GPUs start each frame and does not get faster with more GPUs. | Check the per-frame log; cache heavy deformers and simulations |
| Bucket size | Maxon notes large buckets can reduce performance with multiple GPUs unless the frame is high resolution; default is 128x128. | Keep the default unless you have a reason |
| VRAM per GPU | VRAM is not combined across GPUs; out-of-core data is slower. | Watch the memory in the Feedback Display |
| Mixed GPUs | Each card must still hold the scene, so the smallest card sets the in-VRAM limit. | Use matching GPUs for heavy scenes |
3. How to choose between 2, 4 and 8 GPUs (step by step)
Settings checklist (copy or follow line by line):
Step 1: Check the scene fits one GPU
Open the Feedback Display and watch geometry and texture memory (Maxon: Memory). If the scene does not fit a 24 GB card, use 32 GB RTX 5090 GPUs.
Step 2: Time a frame on 2 GPUs
Render 2 or 3 representative frames and note the seconds per frame.
Step 3: Time the same frames on 4 or 8 GPUs
Compare seconds per frame and cost per frame. If doubling GPUs gives far less than double speed, per-frame overhead is high.
Step 4: Try several frames at once
For long, light sequences, render frame ranges in parallel on subsets of GPUs or on several servers.
Step 5: Plan the full job
Multiply the best cost per frame by your frame count. Our cost guide shows the calculation.
How to read the figure. The badges follow Steps 1 to 5 above. Badge 1 is the memory check in the Feedback Display, badges 2 and 3 are the timings on 2 GPUs and on 4 or 8 GPUs, with speed-up and cost per frame, badge 4 is two jobs on one server chosen with -redshift-gpu, and badge 5 is the plan from the best cost per frame.
Splitting one server into two render jobs
Maxon’s Redshift documentation shows how to choose GPUs for a Cinema 4D command-line render with -redshift-gpu, repeated once per device (Maxon: Command-line Rendering and GPU Selection). The example runs two jobs on a 4-GPU server, each on two GPUs and half of a 200-frame range.
Maxon notes that GPUs chosen on the command line are not written to the Redshift preferences, so Cinema 4D opened normally keeps the devices ticked in the System tab. Maxon support also notes that each machine running the Commandline renderer with Redshift GPU needs its own Redshift license (Maxon: Redshift licenses and render nodes).
How to read the figure. Compare your measured curve with perfect scaling on the chart of seconds per frame for 2, 4 and 8 GPUs: the measured line flattens. The notes beside it repeat the test: check the scene fits 24 GB or use a 32 GB RTX 5090, time 2 GPUs (A) and 4 or 8 GPUs (B), divide A by B, and if doubling GPUs gives far less than double speed, render frame ranges on several servers.
One quick test tells you which way your scene leans:
Checklist: choosing the GPU count
Tick each line as you test, so the full job runs on the server size you measured.
4. How fast are real Redshift jobs on multi-GPU servers?
Recorded iRender jobs: 150 frames rendered in 1h 42m on 4x RTX 5090 (40.84 s per frame), and 360 frames in 1h 18m on 8x RTX 4090. They are different scenes, so they show real job times rather than a scaling curve. Full results are in our Redshift benchmark.
Controlled test: 1x vs 4x RTX 4090 on the same scenes
To measure scaling directly, we timed the same Cinema 4D Redshift scenes on one RTX 4090 and on four, on the same base machine (AMD Ryzen Threadripper PRO 3955WX, 256 GB RAM), at 1920×1080 and 1024 samples:
- Simple scene, adaptive threshold 0.005: 36 s on 1x RTX 4090, 12 s on 4x RTX 4090, so 3.0× faster.
- Complex scene, threshold 0.002: 4 min 19 s on 1x, 1 min 19 s on 4x, so about 3.3× faster.
Neither result reaches 4×. Splitting a frame across GPUs has overhead, the CPU, RAM or disk can become the limit, and a light scene may not keep four GPUs fully busy. In the test, the single card’s usage swung between 50% and 90% on the simple scene and stayed around 80–99% on the complex one, which is why the heavier scene scaled better.
Recorded Redshift jobs on iRender multi-GPU servers.
5. Multi-GPU server or a render farm that splits frames: which fits?
A SaaS render farm usually spreads frames across many machines, so turnaround for a finished scene can be short, and you do not manage hardware. An IaaS render farm such as iRender gives you a whole multi-GPU server: every GPU works on each frame, you can test frames first, and you can rent several servers to split a long sequence. Choose by what the job needs: final scene and shortest turnaround, or testing and control on the render hardware.
On iRender you rent a whole server with 2x, 4x or 8x RTX 5090 or RTX 4090 GPUs, with Cinema 4D and Redshift pre-installed; Prime members get activated Cinema 4D and Redshift licenses. Extra render nodes need their own Redshift license according to Maxon, so check licensing before splitting a job across machines. Real render times are in our Redshift benchmark, and plans are on the Cinema 4D Redshift render farm page.
How to read the figure. The top row is the setup: your own PC or Mac connects by remote desktop to a whole bare-metal server with 1, 2, 4 or 8 GPUs, so you open your Cinema 4D and Redshift project there exactly as at home. The numbered row is the order of a session: register and top up, upload to iRender Drive before the server runs, start and connect, render a test frame and the job, then shut down so billing stops.
6. Redshift multi-GPU FAQ
Does Redshift use multiple GPUs?
Yes. Redshift can use all GPUs in a machine to render each frame, splitting it into buckets. It can also render several frames at once, each on a subset of GPUs.
Does Redshift combine VRAM from multiple GPUs?
No. According to Maxon support, Redshift does not combine VRAM when using multiple GPUs; each GPU can only use its own memory. Data that does not fit is handled out-of-core, which is slower.
Is 8 GPUs twice as fast as 4 GPUs in Redshift?
Not always. Maxon notes that rendering a single frame with all GPUs can give a non-linear gain, and the per-frame scene preparation does not speed up with more GPUs. Test your own scene on both and compare seconds per frame.
Should I render one frame on all GPUs or several frames at once?
Heavy frames usually benefit from all GPUs per frame. Long animations of light frames, where scene preparation is a large share of each frame, can finish sooner by rendering several frames at once on subsets of GPUs.
Can I mix an RTX 5090 and an RTX 4090 for Redshift?
Redshift can use both, but each GPU must hold the scene, so the smaller card’s 24 GB sets the in-VRAM limit for scenes rendered on both.
Do I need a separate Redshift license for each machine?
According to Maxon, the Redshift GPU license in a Cinema 4D subscription covers your main workstation; extra render nodes need their own Redshift license to render on the GPU.





