Published · Phase 2
RTX 5090 Performance at 512, 2K, 8K and 16K Context
On an RTX 5090, 8K–16K is the best default context for 27B–35B models. Move to 32K only for workflows that need it, and treat 64K+ as a measured specialist configuration rather than a free model feature.
Editorial review: complete · Updated 2026-08-30
Plain-English answer
Plain-English answer guidance: On an RTX 5090, 8K–16K is the best default context for 27B–35B models. Move to 32K only for workflows that need it, and treat 64K+ as a measured specialist configuration rather than a free model feature.
Why it matters
Why it matters guidance: 8K is enough for chat and focused coding; 16K–32K suits document/RAG and repository tasks; extreme context belongs to batch analysis with relaxed latency. A sensible ladder is 8K, 16K, 32K, then a workload-specific maximum. Record both prompt-processing and decode rates at each step.
Real StackBench examples
| Configuration | Evidence state | Metric | Source |
|---|---|---|---|
| Qwen3.8-27B · RTX 5090 owner-collected public lab · llama.cpp | Measured · Grade A | 66.8177 tokens/second | StackBench controlled lab approved source qwen38-rtx5090-owner-matrix-20260816 |
| Qwen3.8-27B · RTX 5090 owner-collected public lab · llama.cpp | Measured · Grade A | 68.5936 tokens/second | StackBench controlled lab approved source qwen38-rtx5090-owner-matrix-20260816 |
| Qwen3.8-27B · RTX 5090 owner-collected public lab · llama.cpp | Measured · Grade A | 64.9454 tokens/second | StackBench controlled lab approved source qwen38-rtx5090-owner-matrix-20260816 |
| Qwen3.8-27B · RTX 5090 owner-collected public lab · llama.cpp | Measured · Grade A | 68.1366 tokens/second | StackBench controlled lab approved source qwen38-rtx5090-owner-matrix-20260816 |
Common misconception
Common misconception guidance: The 32 GB memory ceiling makes extreme context and multiple users compete directly with model quality. Model-card context limits do not guarantee useful latency or adequate attention quality at the maximum.
Measured / example table
| Configuration | Evidence state | Metric | Source |
|---|---|---|---|
| Qwen3.8-27B · RTX 5090 owner-collected public lab · llama.cpp | Measured · Grade A | 66.8177 tokens/second | StackBench controlled lab approved source qwen38-rtx5090-owner-matrix-20260816 |
| Qwen3.8-27B · RTX 5090 owner-collected public lab · llama.cpp | Measured · Grade A | 68.5936 tokens/second | StackBench controlled lab approved source qwen38-rtx5090-owner-matrix-20260816 |
| Qwen3.8-27B · RTX 5090 owner-collected public lab · llama.cpp | Measured · Grade A | 64.9454 tokens/second | StackBench controlled lab approved source qwen38-rtx5090-owner-matrix-20260816 |
| Qwen3.8-27B · RTX 5090 owner-collected public lab · llama.cpp | Measured · Grade A | 68.1366 tokens/second | StackBench controlled lab approved source qwen38-rtx5090-owner-matrix-20260816 |
Decision rule
Decision rule guidance: Deploy 16K first. Raise the limit only when real prompts are truncated or retrieval cannot solve the task, then remeasure TTFT, peak memory, and tail latency.
Related benchmarks
Related benchmarks guidance: Observed decode can stay in a similar 65–69 tok/s band across short-to-moderate contexts after prefill, while TTFT and memory rise with prompt length. Long prompts cost time even when steady decode looks stable. Use retrieval, summaries, prompt compaction, or a rolling agent memory. These often outperform feeding an entire repository or document history to every request.
Planner / Explore CTA
Compare this recommendation against your model, context, concurrency, latency, and budget in the ComputeSage Planner.
Sources / methodology
Recommendations combine official specifications, public model/runtime documentation, adjacent benchmark observations, and clearly labeled engineering estimates. Review the ComputeSage evidence methodology.