RTX 6000 Ada
An RTX 6000 Ada runs 28 of the 34 open models tracked here at Q4_K_M with 8k context, computed on 16 October 2026. The largest is Qwen3.6 35B-A3B (MoE), needing 22.4 GB and generating at most 386 tokens per second.
- Memory
- 48 GB VRAM
- Bandwidth
- 960 GB/s
- Board power
- 300 W
- Released
- 2022
- Availability
- Workstation card
Open the RTX 6000 Ada in the LLM checker
What an RTX 6000 Ada runs, model by model
RTX 6000 Ada 48 GB addresses 48 GB at 960 GB/s. Every model below is at Q4_K_M with 8k of context, the setting most people actually use. Once the 5% safety margin comes off, the card has 45.6 GB to spend: memory decides what loads, bandwidth how fast it answers. Both are estimates from stated formulas, and the VRAM calculator shows the working.
On this card a model fits at or under 45.6 GB, and above 40.8 GB it is tight: it loads, but there is little left for the conversation, and a desktop on the same 48 GB can push it over. Tokens per second are single-stream estimates from memory bandwidth; ≤ marks a ceiling real runtimes fall well below.
Computed 16 October 2026The model to actually run on it
Muse Glimmer 30B is the best use of this card: 18.7 GB of the 48 GB available, an estimated 39 tokens per second, comfortable for chat, and 131,072 tokens of context still available.
How this is chosen, since no benchmark is quoted: models are compared by size, a mixture-of-experts model counting at the geometric mean of its total and active parameters (a rule of thumb, not a measurement). The pick is the biggest class that fits with memory to spare and answers at 25 tokens per second or better, and within that class the most recent general-purpose release; coding and reasoning specialists are listed above but not recommended by default.
Qwen3.6 35B-A3B (MoE) is the largest model the card will hold, at 22.4 GB, with room for 131,072 tokens of context. It is a mixture-of-experts model reading only 3B parameters per token, so it is the faster of the two at an estimated 386 tokens per second; what it gives up is the depth of a dense model that reads all of its weights for every token.
It also fits at Q8_0, in about 33.5 GB, which is worth taking whenever the memory allows: Q8 is near-lossless where Q4 costs a little accuracy.
How much context actually fits
Model size is the question people ask; context is the one that bites. The KV cache grows linearly with the conversation, so a model that loads comfortably can still run out of memory halfway through a long document. On 48 GB, the context you get is whatever the weights leave behind, which is why two cards that run the same model can feel completely different in use. These are the largest contexts this card holds, at Q4_K_M weights.
| Model | Max context, FP16 KV | With Q8 KV cache |
|---|---|---|
| Muse Glimmer 30B | 131,072 tokens | 131,072 tokens |
| Qwen3 32B | 40,960 tokens · model limit | 40,960 tokens · model limit |
| Gemma 4 31B | 131,072 tokens | 131,072 tokens |
| Granite 4.2 30B | 104,448 tokens | 131,072 tokens |
Quantising the KV cache to Q8 roughly doubles what you can hold, at a quality cost most people never notice: Granite 4.2 30B on this card goes from 104,448 to 131,072 tokens. Capped at 128k tokens, or at the model's own native window where that is smaller, marked "model limit": free memory beyond that point buys nothing. Rows that hold far more context than their size suggests are hybrid, sliding-window or latent-attention models, which cache only a fraction of what a standard transformer does; each model page shows the working.
Where this card stops
The first model out of reach is Llama 3.3 70B: about 45.8 GB at Q4_K_M and 8k context, against 48 GB of usable memory. That is close enough to be worth a caveat: it is inside the raw 48 GB and only misses the 95% line this site uses for a fit. On a card with a display attached, treat it as no. On a headless card, with a shorter context, it runs. Dropping to Q3_K_M would need about 37.7 GB, which fits, though Q3 loses enough quality that a smaller model at Q4 is usually the better trade. Offloading the remainder to system RAM works and is ten to fifty times slower; it is a way to see a model run, not a way to use one.
Buy or rent
Buy it when the constraint is physical: one machine, under a desk, quiet, 48 GB, no server rack. If the constraint is only capability, renting a 48 GB card for the hours you need it is far cheaper.
Workstation cards are sold on quotes rather than shelf prices, so there is no single number to publish. Put the figure you are actually looking at, with your electricity rate and your real monthly hours, into the build vs rent calculator, which already knows this card draws 300 W under load. It returns the month owning becomes cheaper, or tells you it never does. Hours per month decides it far more often than the price does.
Rented, an RTX 6000 Ada costs from $0.70 an hour (Lium, third-party host), or $0.99 from a provider that runs the machine (RunPod), on demand, before tax, read 19 October 2026. Every provider's price is in the cloud GPU price guide.
The honest take
Forty-eight gigabytes in a normal computer, at 300 watts, without the noise.
This is what you buy when 24 GB is genuinely not enough and the machine has to live under a desk. Forty-eight gigabytes with ECC, in a two-slot blower at 300 W, is a combination no GeForce card offers. Bandwidth is 960 GB/s (between a 3090 and a 4090), so it is not fast for its class. It is capacious and civilised.
What it is good at
- 48 GB is the tier where 70B models come into range. Llama 3.3 70B at Q4 lands within a percent of the memory budget, so it runs on a card with no display attached, with very little context to spare.
- 300 W and a two-slot blower: it fits in a workstation and exhausts its own heat.
- ECC memory and certified drivers, which matter for long fine-tuning runs.
What it is not
- 960 GB/s is lower than a 4090 and far below a 5090. On models that fit both, a 4090 is faster.
- Workstation pricing is several consumer cards for one card's worth of speed.
- Two 3090s reach the same 48 GB for far less, if you can live with the heat, the noise and the split.
The thing people get wrong: It is slower than a 4090 at generating text. You are not buying performance, you are buying a 48 GB address space in a quiet 300 W package, which is exactly the right trade for some people and a waste of money for everyone else.
Compared with the alternatives
- L40S: 48 GB · 864 GB/s · best fit Muse Glimmer 30B at ~35 tok/s. The 48 GB card you meet as a rental line item, not as a purchase.
- RTX PRO 6000 Blackwell: 96 GB · 1,792 GB/s · best fit Llama 3.3 70B at ~31 tok/s. Ninety-six gigabytes and 5090-class bandwidth on one card.
- RTX 4090: 24 GB · 1,008 GB/s · best fit Muse Glimmer 30B at ~41 tok/s. The card most local-model advice is implicitly written for.
All 39 cards are compared side by side on the GPU index, and the same numbers from the model's point of view are on each model fit table. To check one specific pairing rather than read a table, use the can-I-run-it checker.
Questions
- Can an RTX 6000 Ada run a 70B model?
- Not at Q4_K_M in one card. Llama 3.3 70B needs about 45.8 GB at 8k context and this card can address 48 GB. Your options are a smaller model, a harsher quantisation with very little context, splitting across two cards, or renting a larger one for the hours you need it.
- What is the best model to run on an RTX 6000 Ada?
- Muse Glimmer 30B. At Q4_K_M and 8k context it needs about 18.7 GB of the 48 GB available and generates an estimated 39 tokens per second, which is comfortable for chat. It also fits at Q8, at about 33.5 GB, which is worth taking when it fits.
- How many tokens per second does an RTX 6000 Ada generate?
- It depends entirely on the size of the model, because generating a token means reading every active weight out of memory. At 960 GB/s and 70% efficiency, this card produces an estimated 145 tokens per second on an 8B model at Q4, and about 386 on the largest model it holds, Qwen3.6 35B-A3B (MoE). Reading speed is roughly 5 to 8 words per second, so anything above 25 feels immediate. Treat 145 as a ceiling on 960 GB/s rather than a measurement; the higher a figure, the further real runtimes fall below it.
- Is 48 GB enough for running LLMs locally?
- It runs 28 of the 34 models tracked here at Q4_K_M with 8k of context, up to 36B parameters. The honest test is not the model list but the context: Muse Glimmer 30B on this card holds about 131,072 tokens before memory runs out.
- RTX 6000 Ada or L40S for local models?
- Both address about the same memory, so they run the same models. On speed, this card is faster: 960 GB/s against 864 GB/s, and bandwidth is what sets chat speed.
- RTX 6000 Ada or two RTX 3090s for 48 GB?
- Two 3090s reach the same 48 GB for far less money, and can pool it over NVLink. The RTX 6000 Ada gives you that memory in one card, at 300 W, in a two-slot blower that exhausts its own heat, with ECC and certified drivers. You are buying quiet, simple and supported rather than fast: a single 4090 generates text more quickly than this card does.
- Is the RTX 6000 Ada good for fine-tuning?
- It is one of the better single-card options for it: 48 GB with ECC holds training states that consumer cards cannot, and it runs at a power and noise level a desk can live with for the length of a long run. For a run you do once, renting the same capacity is far cheaper.
- Memory: weights (parameters × bytes per parameter) + KV cache (2 × layers × KV heads × head dim × context × bytes for a standard transformer; sliding-window, hybrid and latent-attention models counted as they actually cache) + 0.5 GB runtime + 4% of weights. Full derivation in the VRAM calculator.
- Speed: 70% × bandwidth ÷ active weight bytes, single stream, no batching, prompt processing excluded. A ceiling, not a measurement: the 12 of 28 figures marked ≤ are where real runtimes fall furthest below the number, because so few weights are read per token. See the tokens-per-second estimator.
- Card specification (manufacturer figures): 48 GB, 960 GB/s, 300 W; see NVIDIA's own page for this card. The bandwidth figure: NVIDIA's RTX 6000 Ada datasheet.
- Hourly prices: each provider's own pricing page or price API, read 19 October 2026, as listed in the cloud GPU price guide. Power: the card's full board power at $0.20 a kWh, before the rest of the PC.
- Model architecture values come from each model's published config; the self-hosted LLM guide explains what each one changes.