Use your Nvidia GPU's VRAM as swap space on Linux
tanelpoder
227 points
65 comments
June 02, 2026
Related Discussions
Found 5 related stories in 87.4ms across 9,294 title embeddings via pgvector HNSW
- Valve Developer Improves the Linux Gaming Experience for Limited VRAM Hardware bpierre · 12 pts · April 11, 2026 · 58% similar
- Reminder: Enable ZRAM on your Linux system to optimize RAM usage type0 · 26 pts · April 19, 2026 · 52% similar
- Rotary GPU: Exploring Local Execution for Large MoE Models Under Limited VRAM dryarzeg · 35 pts · May 30, 2026 · 51% similar
- Show HN: A game where you build a GPU Jaso1024 · 610 pts · April 04, 2026 · 49% similar
- Launch HN: Expanse (YC P26) – Unlock Wasted GPU Capacity ismaeel_bashir · 76 pts · June 01, 2026 · 47% similar
Discussion Highlights (19 comments)
simonask
I mean, cool, but I’d rather not?
yjftsjthsd-h
> Built for laptops with soldered memory and no upgrade path. If you have an RTX card sitting there with 8GB of VRAM and you're getting swapped to SSD, this puts that VRAM to work. Well, that does at least answer my immediate question about why I would ever swap from expensive RAM to really expensive RAM:) Feels niche, but when you want it it's a good idea.
jcmfernandes
Q: Why? A: Why not?
xfalcox
Given my dev machine has 32GB of RAM and 32GB of VRAM that sits mostly idle when I'm not running AI models, this is not that bad of an idea.
dragontamer
Remember how 16GBs used to be an enterprise level database mainframe? Well, GPUs also have stupid amounts of compute on them. I have to imagine that there is some kind of database format that's useful with GPU compute attached. Since the data is already in VRAM, the GPU can sort, join, or otherwise manipulate data as needed.
hardwaresofton
You want to waste VRAM, in this economy?
willis936
I'm more interested in the opposite. Nvidia linux drivers crash when you try to address more VRAM than you have. It'd be nice if they didn't.
bobsmooth
RAM disks have always fascinated me. In a different timeline every PC has a 100gb of RAM and 50TB HDDs are the norm.
effnorwood
use your car for an anchor on a big boat!
RachelF
Nice idea, but something has gone very wrong here: >Sequential throughput: ~1.3 GB/s [on a RTX 3070 Laptop] This RTX 3070 chip is on PCIe 4.0 x16 which should give 64GB/s. The 8GB of GDDR6 is 448GB/s. Swapping to an NVMe drive would be twice as fast, but with higher latency.
LouisvilleGeek
Finally a use for the expensive ram when it's not needed in workloads! Now if it could be dynamically used and vacated on other GPU workloads?
UnfitFootprint
No software benchmarks? BAR for RAM is cool but I want to see how much it _actually_ beats pcie nvme
dlt713705
Does anyone these days really use swap for anything than S4 suspend ?
drdaeman
What about backpressure, how does it handle requirements for VRAM allocation when VRAM is used for swap space? With X11 it's not that bad (buffers are pre-allocated), but with Wayland allocations are a lot more dynamic, so running low on VRAM can easily crash the whole desktop. I just had a few of such crashes with Hyprland+llama-server+KVM switching between computers without freeing VRAM.
sgjohnson
>Sequential throughput: ~1.3 GB/s sounds VERY low, also, wouldn't random read/write speed be MUCH more relevant here?
mmastrac
I seriously looked at this as a way to improve the RAM situation in a QNAP 2U unit that I was having trouble sourcing RAM for. It's somewhat annoying that legit memory-over-PCIe is gated on PCIe5 and chipset support. In the end I just had to bite the bullet and take a gamble on finding ECC DDR4 RAM that would work with the ancient AMD chipset... This particular implementation seems to be running over too many layers to be particularly performant. Why not a custom block driver instead?
lowbloodsugar
This is why I read HN.
nialv7
I mean, you prompted something useful out of an AI, good job. But then use that to ask for donation? Feels weird, man.
kimixa
I remember this being a thing done a while back using linux's MTD/phram drivers - https://wiki.archlinux.org/title/Swap_on_video_RAM - not sure if that's still relevant though as I don't know how it'll interact with DRM and how it handles reserving some of the vram - the suggested limit using xorg.conf is probably pretty obsolete now. That page also has a fuse filesystem implementation on top of opencl - https://github.com/Overv/vramfs - which may be more compatible.