Pay attention: a few chats waiting in tray reserve 1GB VRAM for themselves.
Summary
Applications like Discord, Steam, and Telegram reserve VRAM even when minimized, consuming 1GB+ collectively; users working with LLMs should close these apps or disable hardware acceleration to free up VRAM.
Similar Articles
llama.cpp - how to free up even more space on your GPU
A thread sharing practical tips for freeing up GPU memory in llama.cpp, such as offloading mmproj to CPU and adjusting KV cache types, while discussing parameters like --cache-type-k/v and --spec-draft-n-max.
@sudoingX: save this one. it answers a question every 24gb GPU owner asks and almost nobody gets right. how much context can i act…
A user shares detailed VRAM usage measurements for running Qwen 3.6 27b on a 24GB GPU, showing context window sizes and headroom, and notes that a used RTX 3090 performs identically to newer cards.
GPU Memory Math for LLMs (2026 Edition)
A practical guide explaining how to calculate VRAM requirements for LLMs based on parameter count and quantization level, plus additional overhead from KV cache, activations, and batching.
@sudoingX: anyone running a 16gb card, stop scrolling. @pupposandro and @davideciffa got qwen 35b-a3b down to 13.3gb, measured on …
A technique called luce spark allows Qwen 35B-a3B MoE model to run on a 16GB GPU (like RTX 3090) by learning which experts are frequently used and streaming the rest from RAM, achieving ~100 tok/s without VRAM bottleneck.
Local LLM CPU users... How long is it taking you to do anything?
A discussion about the performance of running large language models locally on CPU, especially with large context sizes, and the challenges of VRAM constraints.