October 28, 2026 Vivian Vu

Mixing RTX 5090 and RTX 4090 for Rendering: VRAM Limits and Setup in Octane, Redshift, Cycles and Karma XPU

Executive SummaryKey Takeaways: Mixing RTX 5090 and RTX 4090 for Rendering
VRAM • Speed • Setup

You can render with an RTX 5090 and an RTX 4090 together, with one firm limit:

  • It works: Octane, Redshift, Cycles and Karma XPU all accept mixed NVIDIA GPUs in one machine.
  • VRAM is per card: Every rendering GPU holds the full scene, so the pair renders in-core only up to 24 GB.
  • Above 24 GB: Use the 5090 alone, or rely on out-of-core / system-memory fallback at a speed cost.
  • Best use of both: Render one frame per GPU from the command line, as Maxon suggests for multi-GPU machines.
  • On iRender: Identical GPUs in every server: 2x, 4x or 8x RTX 5090 (32 GB each) or RTX 4090 (24 GB each), never mixed.

Adding a new RTX 5090 next to an existing RTX 4090 is a common upgrade. It does speed up rendering, but it does not give you 56 GB of VRAM, and heavy scenes behave differently in each engine. This guide uses each vendor’s documentation to explain what to expect and how to get the most from a mixed pair.

Checked against Maxon, OTOY, Blender, SideFX and NVIDIA documentation, November 2026.

1. Can you mix an RTX 5090 and an RTX 4090?

Yes. In Puget Systems’ tests, mixed GPUs worked in both Octane and Redshift and the speed gain was in line with using matching cards; the catch they noted is that you are limited to the card with the least memory. The two cards differ mainly in memory size and bandwidth (NVIDIA RTX 5090, NVIDIA RTX 4090):

SpecsRTX 5090 vs RTX 4090

The two cards side by side

From NVIDIA's product pages.

SpecRTX 5090RTX 4090
VRAM32 GB GDDR724 GB GDDR6X
Memory bandwidth1,792 GB/s1,008 GB/s
ArchitectureBlackwellAda Lovelace
PCIePCIe 5.0PCIe 4.0
Graphics card power575 W450 W
Mixed pairRendering together, both cards must hold the same scene, so the usable in-core limit is 24 GB.

2. Why don't 32 GB and 24 GB add up?

GPU renderers copy the whole scene to every GPU that renders it, so a mixed pair renders in-core only up to the smaller card’s 24 GB.

iRender
What a mixed pair renders in-core
MIXED VRAM
Scene up to 24 GBRTX 509032 GBRTX 409024 GBin-core on both cardsScene 24 to 32 GBRTX 509032 GBRTX 409024 GB4090: out-of-core, or untick itScene above 32 GBRTX 509032 GBRTX 409024 GBout-of-core on bothEach card holds its own copy of the scene, so the smaller card sets the in-core limit for the pair
In-coreOut-of-core, or untick the card
From Maxon, OTOY, Blender and SideFX documentation

How to read the figure. Each row is one scene size on the same pair of cards. Up to 24 GB, the scene fits in-core on both the RTX 5090 and the RTX 4090. Between 24 and 32 GB it fits in-core on the 5090, while the 4090 needs out-of-core or should be unticked. Above 32 GB both cards need out-of-core. Because each card holds its own copy, the smaller card sets the in-core limit for the pair.

Memory per GPUWhy 32 GB + 24 GB is not 56 GB

A 26 GB scene on a mixed pair

Each GPU receives its own full copy of the scene. Illustrative example; real limits depend on the engine and on VRAM already used by the system.

SYSTEM RAM  [geometry · textures · BVH]
│ copied to every rendering GPU
├──▸ RTX 5090 · 32 GB → 26 GB scene fits, about 6 GB left
└──▸ RTX 4090 · 24 GB → 26 GB does not fit
      ├─ out-of-core on → data paged from system RAM, slower
      └─ out-of-core off → the card cannot render this scene

A note on sources about VRAM: Maxon's support article states that Redshift does not combine the VRAM when using multiple GPUs. Maxon's 3D rendering product page also lists "multi-GPU memory pooling" and says Redshift shares out-of-core memory across multiple cards. This article follows the support article: plan for every GPU holding the scene in its own VRAM. Check Maxon's latest documentation for your Redshift version.

3. How do Octane, Redshift, Cycles and Karma XPU handle a mixed pair?

EnginesMixed GPUs per Engine

What each vendor documents

Quoted or summarized from each vendor's own documentation.

EngineVRAM across GPUsWhen a GPU runs out
RedshiftNot combined (an 8 GB + 12 GB pair is not 20 GB)Out-of-core rendering, so the largest scene is not limited by the weakest GPU
OctaneLimited to the VRAM of the smallest GPUOut-of-core keeps textures and geometry in system RAM; OTOY recommends disabling GPUs without enough VRAM
CyclesEach GPU can only access its own memoryCUDA, OptiX, HIP and Metal try system memory automatically, with a speed cost
Karma XPUEach device addressed separately; memory not pooledIf a device fails, other devices (including the CPU) finish the frame
RuleMixing works; adding a smaller card adds speed, not scene capacity.

4. How to use both cards well (step by step)

Step 1: Render heavy scenes on the RTX 5090 only

When a scene is over 24 GB, untick the RTX 4090 for rendering so the scene stays in-core on the 32 GB card:

Settings checklist
Redshift (C4D) → Edit › Preferences › Renderer › Redshift › Compute Devices
untick the RTX 4090
Octane → Preferences › Devices › Render: RTX 5090 only
(the RTX 4090 can stay ticked for Denoise)
Cycles → Preferences › System › Cycles Render Devices › OptiX
untick the RTX 4090
Karma XPU → KARMA_XPU_DEVICES = list of device IDs to enable

Menu sources: Maxon, OTOY, Blender, SideFX. Karma XPU shows device IDs in its render stats.

Step 2: Or render one frame per GPU

Maxon notes that giving each job a subset of GPUs lets you render several frames at once on one machine for better scaling (Maxon). Each card then works at its own speed and keeps its own memory limit. Run the two commands in two terminals:

iRender
Two cards, two jobs
SPLIT FRAMES
Job A · GPU 0RTX 5090even frames: 0, 2, 4 …32 GB limit, its own speedJob B · GPU 1RTX 4090odd frames: 1, 3, 5 …24 GB limit, its own speedOne output folder0123456789sequence complete; no waiting for the slower cardcheck each GPU with nvidia-smiMaxon suggests giving each job a subset of GPUs for better scaling on one machine
RTX 5090RTX 4090Result
From Maxon, OTOY and Blender command-line documentation

How to read the figure. Follow the two jobs into one output folder. Job A runs on GPU 0, the RTX 5090 with its 32 GB limit, and renders the even frames; job B runs on GPU 1, the RTX 4090 with its 24 GB limit, and renders the odd frames. Each card works at its own speed, and the numbered strip shows the sequence filling in without waiting for the slower card.

Cinema 4D + Redshift // Commandline2 jobs
# Job A: RTX 5090 (GPU 0), even frames
Commandline.exe -redshift-gpu 0 -render C:\project\scene.c4d -frame 0 98 2
# Job B: RTX 4090 (GPU 1), odd frames
Commandline.exe -redshift-gpu 1 -render C:\project\scene.c4d -frame 1 99 2
# Alternative: environment variable, read when Redshift starts
set REDSHIFT_GPUDEVICES=0
Octane Standalone // octane-cliper GPU
# -g adds a GPU (0 = first), -t render target, -e exit when done
octane-cli.exe -g 0 -t "RenderTarget" -e C:\project\scene.ocs
# Second job on the RTX 4090
octane-cli.exe -g 1 -t "RenderTarget" -e C:\project\scene2.ocs
Blender Cycles // background render2 jobs
# Job A: first OptiX GPU, frames 1, 3, 5 ... (-j = frame step)
blender -b scene.blend --python-expr "import bpy;p=bpy.context.preferences.addons['cycles'].preferences;p.compute_device_type='OPTIX';p.get_devices();g=[d for d in p.devices if d.type=='OPTIX'];[setattr(d,'use',False) for d in p.devices];g[0].use=True;bpy.context.scene.cycles.device='GPU'" -s 1 -e 100 -j 2 -a
# Job B: second OptiX GPU, frames 2, 4, 6 ...
blender -b scene.blend --python-expr "import bpy;p=bpy.context.preferences.addons['cycles'].preferences;p.compute_device_type='OPTIX';p.get_devices();g=[d for d in p.devices if d.type=='OPTIX'];[setattr(d,'use',False) for d in p.devices];g[1].use=True;bpy.context.scene.cycles.device='GPU'" -s 2 -e 100 -j 2 -a

Sources: Maxon command-line GPU selection, Redshift environment variables, OTOY command line, Blender command line. Check which index belongs to which card in each app before running.

Step 3: Keep out-of-core on for large scenes

If you render with both cards above 24 GB, enable out-of-core: in Octane, Preferences › Application › Enable Out-Of-Core Data with a System RAM Usage Limit (OTOY); Redshift uses out-of-core automatically (Maxon). Expect slower frames than in-core.

iRender
Using an RTX 5090 and RTX 4090 together: three steps
D1
Redshift › Compute DevicesRTX 5090 (32 GB)RTX 4090 (24 GB): untick for scenes over 24 GB1Two jobs, one GPU eachJob A · GPU 0RTX 5090: even frames2Job B · GPU 1RTX 4090: odd framesOctane › Preferences › ApplicationEnable Out-Of-Core Data3System RAM Usage Limit setRedshiftout-of-core is automatic
Setting to change
Mockup based on Maxon and OTOY documentation

How to read the figure. The badges follow Steps 1 to 3 above. Badge 1 is the RTX 4090 unticked in Redshift’s Compute Devices so a scene over 24 GB renders on the RTX 5090 only. Badge 2 is the split into two jobs with one GPU each, even frames on the 5090 and odd frames on the 4090. Badge 3 is Enable Out-Of-Core Data in Octane, with its System RAM Usage Limit; Redshift uses out-of-core automatically.

Quick check: during a test frame, nvidia-smi shows each job on its own GPU and memory below that card's total.

5. Mixed pair at home or identical GPUs on a farm: SaaS or IaaS?

A SaaS render farm takes the scene as a job and manages the hardware for you, which suits standard scenes and supported plugins. An IaaS render farm such as iRender rents you a whole server with identical GPUs, 2x, 4x or 8x RTX 5090 (32 GB each) or RTX 4090 (24 GB each), so every card has the same memory limit and you choose the devices yourself. See SaaS vs IaaS render farm and multi-GPU render engines for Cinema 4D.

iRender
How iRender works: your computer controls your own multi-GPU server
IaaS render farm
Your PC or MacNo powerful GPU neededRemote desktopLive screen1:1 like your PCYOUR OWN GPU SERVERbare-metal · not sharedGPUGPUGPUGPUGPUGPUGPUGPU1, 2, 4 or 8 × RTX 5090 (32 GB) or RTX 4090 (24 GB)Threadripper PRO · 256 GB ECC RAM · 2 TB NVMe SSDFull admin access · your setup is saved between sessions1Register, top upFirst $50+ top-up doubled2Upload your projectiRender Drive, free3Start and connectRemote desktop, any OS4Render, shut downBilling stops, per minute✓ Your workstation, just more GPUs: no queue to wait, no farm plugin, no job submission, no settings changed
Your mouse and keyboardServer screen streamed back
Schematic, not to scale

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, Blender or Houdini 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.

Multi-GPU rendering on iRender servers with identical GPUs.

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. Real render times are in our Redshift benchmark, and plans are on the Cinema 4D Redshift render farm page.

6. Mixed GPU rendering FAQ

Can I use an RTX 5090 and an RTX 4090 together for rendering?
Yes. Octane, Redshift, Cycles and Karma XPU all work with mixed NVIDIA GPUs. The pair is faster than either card, but every card must hold the scene.

Do an RTX 5090 and RTX 4090 combine to 56 GB of VRAM?
No. Each rendering GPU keeps its own copy of the scene, so the in-core limit is the smaller card: 24 GB. Maxon, OTOY, Blender and SideFX all document that VRAM is not pooled.

What happens when my scene is bigger than 24 GB?
Redshift and Octane can use out-of-core memory and Cycles falls back to system memory, all slower than in-core. Karma XPU lets the other devices finish the frame if one GPU fails. Rendering on the RTX 5090 alone keeps a scene up to about 32 GB in-core.

Does the slower RTX 4090 slow down the RTX 5090?
The pair is still faster than one card; Puget Systems found mixed cards scaled in line with expectations in Octane and Redshift. Test your own scene, because results vary by engine and scene.

How do I render one frame per GPU?
Start two command-line renders, each limited to one GPU: -redshift-gpu for Cinema 4D with Redshift, -g for Octane Standalone, a device setting via –python-expr for Blender, or KARMA_XPU_DEVICES for Karma XPU, each with its own frame range.

Does iRender mix GPU models in a server?
No. Each iRender server has identical GPUs: 1, 2, 4 or 8 RTX 4090 cards, or 1, 2, 4 or 8 RTX 5090 cards.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , ,

Vivian Vu

Vivian Vu has written nearly 40 articles for the iRender blog, covering iRender news, Maya, Blender and real-time rendering.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →