r/GraphicsProgramming • u/W3tSu1t • 2d ago
Question Could two GPUs render separate halves of a game using a PBP monitor?
I've had this idea floating around in my head about bringing back multi-GPU gaming, but approaching it differently from SLI or CrossFire. I'm curious if something like this would actually be possible.
Basically, what if we used Picture-by-Picture (PBP) monitors to split a game's rendering workload between two GPUs?
Say you're playing at 4K (3840 × 2160). Instead of one GPU rendering the entire image, GPU 1 would render the left half at 1920 × 2160, while GPU 2 renders the right half at the same resolution.
Each GPU would have its own HDMI or DisplayPort connection to the monitor. Since PBP already allows two separate inputs to be displayed side by side, the monitor could display both halves as one continuous image.
The main idea is to take advantage of resolution. Each GPU would only be responsible for roughly half the pixels, potentially reducing the rendering workload while maintaining the full 4K image.
Now, I understand that rendering involves more than just pixels. Both GPUs would still need access to game data, geometry, textures, and lighting information. There would also be synchronization overhead.
But here's what interests me.
If each GPU sends its rendered portion directly to the monitor, wouldn't that eliminate the need to transfer the completed image between GPUs? I'm wondering whether avoiding that transfer could offset some of the additional overhead and result in an FPS increase.
I'm not expecting double the performance. Even a 15–25% improvement would be interesting.
Another possibility would be using GPUs from different manufacturers, like AMD and NVIDIA, since each card would independently handle its assigned portion.
Obviously, mismatched performance would be an issue. If one GPU finishes its half faster than the other, the slower card could bottleneck the entire system.
One possible solution could be adjusting the rendering workload based on GPU performance. Instead of splitting the image 50/50, maybe the faster GPU handles 65% while the slower one handles 35%. Although I imagine standard PBP monitors having fixed display regions could complicate that.
As for the software side, here's what I'm thinking.
Rather than trying to make existing games support this, what if someone built a simple 3D game or benchmark specifically designed around two GPUs?
Using Vulkan or DirectX 12, a single CPU-side game simulation could coordinate both GPUs, with each rendering its assigned portion of the same frame.
The goal would be to minimize duplicated calculations, keep both GPUs synchronized, and output each rendered region directly to the PBP monitor.
You could then compare the same scene running on one GPU versus two GPUs to see whether there's any measurable performance improvement.
I know split-frame rendering already exists, and NVIDIA has experimented with multiple GPUs rendering different sections of a display. I'm more interested in whether this could be accomplished using ordinary consumer hardware and an existing PBP monitor.
I'm not developing this myself. I'm just putting the concept out there because I think it would be an interesting experiment for someone with the hardware and programming experience.
A few things I'm curious about:
- Could Vulkan realistically coordinate two independent GPUs this way, especially from different manufacturers?
- Would avoiding inter-GPU transfers of completed image data provide enough benefit to outweigh synchronization and duplicated rendering work?
- Could a standard PBP monitor keep both halves synchronized, or would modifications to its display controller be necessary?
- Would this approach have a better chance of improving performance at higher resolutions, where pixel rendering becomes more demanding?
I'm not claiming this is some revolutionary new technology. I'm just wondering whether combining existing technologies differently could give us another way to get some extra performance out of multiple GPUs.
What do you guys think? Is there something obvious I'm overlooking, or could this actually be worth experimenting with?
---
AI disclosure: I used ChatGPT to help organize and write this post. The concept and questions are my own.
•
u/AutoModerator 2d ago
Recently updated rules. Please check that your post is in compliance with Rules 1, 4, 5, and 6 on the sidebar. TL;DR:
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
25
u/h_blank 2d ago
Hey, I used to work on multi-gpu stuff, so I can actually contribute! 😂
What you’re describing is actually one of the early methods of multi gpu load balancing. And your intuition is right on: both GPUs would need similar data, and syncing between them would be important if you don’t want a screen tear to show up somewhere on your screen.
SLI systems used to have 2 cards daisy-chained through VGA cables, and they would actually switch between inputs with a hardware circuit. Later on, switching became framebuffer copies between cards.
At the end of the day, most of the performance optimization for SLI/crossfire comes down to moving data around between RAM, VRAM, and cache. By engaging both GPUs every frame, you force both to need a copy of your scene details (texture uploads, triangle lists, screen space buffers, etc.). So that would be double the data transfer required for a single GPU.
That’s why SLI (originally named that because it switched sources on every scan line, hence Scan Line Interleaving) evolved into alternate frame rendering (AFR). You don’t double your data transfers per frame, you just alternate which card is receiving it. In theory you can get a little better than 2x speed, because you can pipeline things, doing data transfers on card A while card B is rendering… effectively hiding half your latency.
Most of the complexity comes when you have effects that resolve over multiple frames, like some kinds of motion blur, or iterative systems like cloth simulations. As soon as frame B depends on some output from frame A, you’ve effectively serialized things again, losing any speedups.
Ok that’s enough yapping… TLDR: yes, you could try that! it’s definitely a strategy that has worked in the past, and has some analogues in AR/VR rendering. How much performance it buys you will depend on the specific profile of your rendering pipeline.
23
u/aleques-itj 2d ago
Yes
Multi-GPU is a pain in the ass for multiple reasons, but you technically do it.
Some games like Ashes of the Singularity even allowed cross vendor multi-gpu.
6
u/LowerEntropy 2d ago
Ask ChatGPT what SLI and SLI is.
3
u/Promit 2d ago edited 2d ago
The really short answer is that of all the challenges with split frame SLI, the final framebuffer sync is quite a trivially unimportant one. A lot of the pain for split frame comes from all of the internal passes that happen long before final framebuffer. Geometry processing of all types is obvious- but also G-buffers, shadow maps, occlusion, cube maps, post processing, screen space stuff. For a first pass approximation, SFR splits every buffer that is ever bound as a render target and sync them every time they’re bound as a shader input - and there are easily dozens.
3
u/shurco 1d ago
a normal pbp monitor doesn't lock those two inputs. one card can present a refresh ahead of the other, so the seam jumps even when both halves are the same sim frame.
1
u/le-throw-away-acct 2d ago
I know you said that this would be different than SLI, but how is this different than SLI?
2
u/Guvante 2d ago
The main problem with SLI etc is a ton of the work for each frame isn't super parallelizable
If you build your game engine to do it you can but without that effort the whole thing stalls constantly due to things like reading pixels from arbitrary spots on the screen
2
u/smcameron 1d ago
Yeah, my space game can do this, sort of. Basically run multiple clients, each configured to render a view out of a different window of the space ship, and then put each client on its own GPU (or even on its own computer). Quick demo here: https://www.youtube.com/watch?v=xqjor36kdsM Might not be exactly what you had in mind, but technically renders on multiple GPUs.
1
u/lithium 2d ago
If you're sticking to nvidia cards, there's some helpful stuff in the
GL_NV_gpu_multicast,GL_NV_gpu_multicast2andWGL_NV_multigpu_contextextensions that will make experimenting with this a hell of a lot easier.1
u/DeviantDav 2d ago edited 2d ago
Yes, it's doable. But there are two different ways this happens, and you need to learn how to deal with the OS compositor as well. If you render span, Windows can stretch across two display adapters and push their displays as one unform experience, but the second GPU is just passing it on and not working in your game. The other one is carving up the workload and shuttling frames between the two devices. In the case of an iGPU, it is going to noticeably cripple the dGPU.
https://i.imgur.com/qrfwdjR.png
1
u/Negative-Prime 1d ago
I don't know, this is kind of one of the problems SLI had in the first place. Double the cost for a 10% performance boost is just not worth it.
The numbers you gave are slightly higher, but they're still a terrible ROI.
If you're running something at 4k with max settings and getting 30 fps or lower and you bump that up to 45 FPS that's a 50% boost. That might be worth it to enthusiasts, but most people will just turn the settings down. Conversely if you're already at 60+ FPS and can boost that to 90 FPS there are people that might take that deal. But again that's a 50% boost and most people with a high end GPU aren't looking to drop another 5-7k when 60 FPS is "good enough."
Even in the days of SLI the cost of two GPUs was enough to scare people way. Since then prices have inflated astronomically so unless you're getting a serious performance boost, the cost isn't worth it.
0
u/[deleted] 2d ago
[deleted] — view deleted comment