Muse Glimmer 30B VRAM requirements
Muse Glimmer 30B needs about 19.2 GB of VRAM at Q4_K_M with 8K context, so it fits a 24 GB card such as the RTX 3090 or the RTX 4090. Muse Glimmer 30B has 29.8B parameters. With the same 8K context and one request it needs 31.2 GB at FP8 and 61.7 GB at FP16/BF16. The published weights take 55.5 GB (BF16). The smallest setup here that holds it at Q4_K_M with an 8K context is the RTX 3090 (24 GB), which runs it with its full 128K-token context.
19.2 GB at Q4_K_M, 8K context, one request
- FP8
- 31.2 GB
- FP16 / BF16
- 61.7 GB
- Published weights
- 55.5 GB
- Smallest setup, Q4_K_M
- RTX 3090 (24 GB)
Worked example: Muse Glimmer 30B with 32K tokens
Inputs: Muse Glimmer 30B · Q4_K_M weights · 32,768 tokens of context · one request · FP16 KV cache
- Weights (29.8B at Q4_K_M)
- 16.8 GB
- KV cache (13 KB per token)
- 514 MB
- Buffers and runtime (0.5 GB + 10%)
- 2.23 GB
- Total
- 19.5 GB
The smallest setup here that holds it is the RTX 3090 (24 GB), with about 4.49 GB to spare. Change the inputs in the calculator
What makes Muse Glimmer 30B's memory use different
Its 39 sliding-window layers keep only the last 2,048 tokens (llama.cpp gives them 2,560 cells: the window plus a 512-token batch, rounded up to 256): at its 128K limit they hold 98 MB of cache instead of the 4.88 GB they would need with full attention.
Per token of context it adds 13 KB of FP16 cache; Granite 4.2 30B (29.3B), the nearest-sized model here with plain full attention, adds 256 KB, so Muse Glimmer 30B needs 5% as much.
How much VRAM does Muse Glimmer 30B need?
Muse Glimmer 30B needs 19.2 GB at Q4_K_M, 33.1 GB at Q8_0 and 61.7 GB at FP16 with 8,192 tokens of context and one request. Each total below is the weights plus the FP16 KV cache and the runtime overhead (0.5 GB plus 10%), and each row opens the calculator with that setting. What the GGUF names mean.
| Precision | Weights | Total | Smallest setup |
|---|---|---|---|
| As published (BF16) | 55.5 GB | 61.7 GB | 2× RTX 5090 (64 GB) |
| FP16 / BF16 | 55.5 GB | 61.7 GB | 2× RTX 5090 (64 GB) |
| FP8 / INT8 | 27.7 GB | 31.2 GB | RTX 5090 (32 GB) |
| INT4 (AWQ / GPTQ) | 14.7 GB | 16.9 GB | RTX 3090 (24 GB) |
| GGUF Q8_0 | 29.5 GB | 33.1 GB | M4 Pro Mac (64 GB, 48 GB usable) |
| GGUF Q6_K | 22.7 GB | 25.7 GB | RTX 5090 (32 GB) |
| GGUF Q5_K_M | 19.7 GB | 22.3 GB | RTX 3090 (24 GB) |
| GGUF Q4_K_M | 16.8 GB | 19.2 GB | RTX 3090 (24 GB) |
| GGUF IQ4_XS | 15.1 GB | 17.3 GB | RTX 3090 (24 GB) |
| GGUF Q3_K_M | 13.6 GB | 15.6 GB | RTX 4060 Ti 16GB |
| GGUF IQ3_XXS | 11.4 GB | 13.3 GB | RTX 4060 Ti 16GB |
| GGUF Q2_K | 11.6 GB | 13.5 GB | RTX 4060 Ti 16GB |
Fine-tuning Muse Glimmer 30B? Muse Glimmer 30B VRAM for LoRA, QLoRA and full training.
Muse Glimmer 30B GGUF files on Hugging Face
The 8 GGUF files llama.cpp picks for Muse Glimmer 30B with -hf <repo>:<QUANT>, with the bytes the Hugging Face file list reported on 2026-09-29. Each total is that file plus the FP16 KV cache and 0.5 GB + 10%, one request. "vs estimate" compares the file with the bits-per-weight size the table above uses.
| Quant | File | Size | vs estimate | 8K | 32K | 128K |
|---|---|---|---|---|---|---|
| Q2_K | bartowski/ | 10.3 GB11,035,579,936 bytes | −11% | 12.0 GB | 12.4 GB | 13.7 GB |
| Q3_K_M | bartowski/ | 13.0 GB13,962,519,328 bytes | −4% | 15.0 GB | 15.4 GB | 16.7 GB |
| IQ4_XS | bartowski/ | 14.4 GB15,435,096,096 bytes | −5% | 16.5 GB | 16.9 GB | 18.2 GB |
| Q4_K_M | bartowski/ | 16.1 GB17,306,324,000 bytes | −4% | 18.4 GB | 18.8 GB | 20.1 GB |
| Q5_K_M | unsloth/ | 17.9 GB19,194,274,848 bytes | −9% | 20.4 GB | 20.7 GB | 22.1 GB |
| Q6_K | bartowski/ | 21.8 GB23,414,418,720 bytes | −4% | 24.7 GB | 25.0 GB | 26.4 GB |
| Q8_0 | unsloth/ | 27.6 GB29,612,957,984 bytes | −6% | 31.1 GB | 31.4 GB | 32.7 GB |
| BF16 | unsloth/ | 51.9 GB55,725,511,168 bytes | −6% | 57.8 GB | 58.1 GB | 59.5 GB |
GB here is GiB (1024³ bytes), as everywhere on this site; Hugging Face shows the Q4_K_M file as 17.3 GB, in 10⁹ bytes.
Which Muse Glimmer 30B GGUF fits a 16, 24, 32, 48 or 80 GB GPU or a Mac
From the file sizes above: the largest file that fits each machine with an 8K context and 0.5 GB left free, the longest context it then has room for, and the longest context for Q4_K_M (16.1 GB). One request, FP16 KV cache, -np 1. The Q4_K_M file is 676 MB under its bits-per-weight estimate; the estimate tables and the llama-server command on this page count the estimate, so they show less context.
| Hardware | Largest GGUF, 8K | Its longest context | Q4_K_M, longest context |
|---|---|---|---|
| RTX 5060 Ti 16GB | Q3_K_M, 13.0 GB | 42K | No |
| RTX 4090 (24 GB) | Q5_K_M, 17.9 GB | 128K (full) | 128K (full) |
| RTX 5090 (32 GB) | Q8_0, 27.6 GB | 39K | 128K (full) |
| L40S (48 GB) | Q8_0, 27.6 GB | 128K (full) | 128K (full) |
| H100 SXM (80 GB) | BF16, 51.9 GB | 128K (full) | 128K (full) |
| M4 Pro Mac (64 GB, 48 GB usable) | Q8_0, 27.6 GB | 128K (full) | 128K (full) |
| M4 Max Mac (128 GB, 96 GB usable) | BF16, 51.9 GB | 128K (full) | 128K (full) |
Run Muse Glimmer 30B with llama.cpp
llama-server -hf bartowski/Muse-Glimmer-30B-GGUF:Q4_K_M -c 131072 -np 1 Muse-Glimmer-30B-Q4_K_M.gguf, 17.3 GB, from bartowski/
Muse Glimmer 30B at 8K, 32K and 128K (full) tokens of context
13 of its 52 layers use full attention and 39 keep a sliding window of 2,048 tokens. Each extra token of context adds 13 KB of FP16 cache per request once the sliding windows are full. The last column is the smallest setup here, one card or a group, that holds it at Q4_K_M. How the KV cache works.
| Context | KV cache, FP16 | Total at Q4_K_M | Total at Q8_0 | Smallest setup, Q4_K_M |
|---|---|---|---|---|
| 8K tokens | 202 MB | 19.2 GB | 33.1 GB | RTX 3090 (24 GB) |
| 32K tokens | 514 MB | 19.5 GB | 33.5 GB | RTX 3090 (24 GB) |
| 128K tokens | 1.72 GB | 20.8 GB | 34.8 GB | RTX 3090 (24 GB) |
How fast Muse Glimmer 30B writes
Tokens per second for one request with 8,192 tokens of context, estimated from memory bandwidth. A dash means it does not fit on one card. Try other settings in the speed calculator.
| Hardware | Bandwidth | Q4_K_M | FP8 |
|---|---|---|---|
| RTX 3060 12GB | 360 GB/s | — | — |
| RTX 4090 | 1,008 GB/s | 29–41 | — |
| RTX 5090 | 1,792 GB/s | 50–71 | 31–44 |
| M4 Max Mac (128 GB) | 546 GB/s | 16–22 | 9.9–14 |
| M3 Ultra Mac Studio (512 GB) | 819 GB/s | 24–33 | 15–20 |
| H100 SXM | 3,350 GB/s | 88–129 | 56–80 |
| H200 | 4,800 GB/s | 119–180 | 78–113 |
Longest context on one GPU
How many tokens of context Muse Glimmer 30B fits on a single card with one request, an FP16 KV cache and 0.5 GB left free. "Full" means the model's whole context window fits.
| GPU | Memory | Q4_K_M | Q8_0 | FP8 |
|---|---|---|---|---|
| RTX 3060 | 12 GB | No | No | No |
| RTX 4060 Ti 16GB | 16 GB | No | No | No |
| RTX 3090 / 4090 | 24 GB | 128K (full) | No | No |
| RTX 5090 | 32 GB | 128K (full) | No | 27K |
| A100 40GB | 40 GB | 128K (full) | 128K (full) | 128K (full) |
| Mac, 64 GB unified memory | 48 GB | 128K (full) | 128K (full) | 128K (full) |
| L40S / RTX 6000 Ada | 48 GB | 128K (full) | 128K (full) | 128K (full) |
| A100 / H100 80GB | 80 GB | 128K (full) | 128K (full) | 128K (full) |
| Mac, 128 GB unified memory | 96 GB | 128K (full) | 128K (full) | 128K (full) |
| H200 | 141 GB | 128K (full) | 128K (full) | 128K (full) |
| B200 | 180 GB | 128K (full) | 128K (full) | 128K (full) |
Model details
- Parameters
- 29.8B (29,776,626,688)
- Layers
- 13 of its 52 layers use full attention and 39 keep a sliding window of 2,048 tokens
- Attention cache
- 2 KV heads × 128
- Context length
- 131,072 tokens
- Published weights
- 55.5 GB (BF16)
- On Hugging Face
- meta-models/
Muse-Glimmer-30B - Reported benchmarks
- None published in the model card for GPQA, MMLU-Pro or LiveCodeBench.
Why this estimate looks this way
At Q4_K_M and an 8K-token context, Muse Glimmer 30B uses 16.8 GB for weights, 202 MB for its FP16 KV cache and 2.20 GB for estimated runtime overhead, totaling 19.2 GB. The overhead is a 0.5 GB base plus 10% of weights and cache.
Its attention layout matters for long context: 13 of its 52 layers use full attention and 39 keep a sliding window of 2,048 tokens. The FP16 cache grows by about 13 KB per additional token per request once the sliding windows are full.
The architecture and published checkpoint size come from the model's config.json and weight files. These are estimates rather than measured peak memory; inference engines can reserve extra buffers or preallocate the full configured cache.
Muse Glimmer 30B next to similar-sized models
The three models here closest to it in parameter count, at Q4_K_M with 8,192 tokens of context.
| Model | Parameters | Total | KV per token | Smallest setup |
|---|---|---|---|---|
| Muse Glimmer 30B | 29.8B | 19.2 GB | 13 KB | RTX 3090 (24 GB) |
| Granite 4.2 30B | 29.3B | 20.8 GB | 256 KB | RTX 3090 (24 GB) |
| Qwen3-Coder 30B-A3B | 30.5B, 3.3B active | 20.2 GB | 96 KB | RTX 3090 (24 GB) |
| Qwen3 30B-A3B | 30.5B, 3.3B active | 20.2 GB | 96 KB | RTX 3090 (24 GB) |
Muse Glimmer 30B VRAM questions
How much VRAM do I need to run Muse Glimmer 30B locally?
About 19.2 GB at Q4_K_M with an 8K context and one request, by the bits-per-weight estimate, and 61.7 GB at BF16. The Q4_K_M GGUF Muse-Glimmer-30B-Q4_K_M.gguf in bartowski/
Can I run Muse Glimmer 30B on a 24 GB GPU?
Yes. On the RTX 4090 (24 GB), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q5_K_M (17.9 GB), with its full 128K-token context.
Which quantization of Muse Glimmer 30B fits in 16 GB of VRAM?
On the RTX 5060 Ti 16GB, the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q3_K_M (13.0 GB), with up to 42K tokens of context.
Can I run Muse Glimmer 30B on a Mac?
On the M4 Pro Mac (64 GB, 48 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q8_0 (27.6 GB), with its full 128K-token context. On the M4 Max Mac (128 GB, 96 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is BF16 (51.9 GB), with its full 128K-token context. By default macOS lets the GPU use about 75% of unified memory.
How much more VRAM does Muse Glimmer 30B need for 32K or 128K tokens of context?
Its FP16 KV cache is 202 MB at 8K, 514 MB at 32K, 1.72 GB at 128K for one request, so 128K adds 1.52 GB over 8K, plus 10% overhead. A q8_0 cache
Why does Muse Glimmer 30B use more VRAM than its GGUF file size?
The file holds only the weights. At Q4_K_M with an 8K context: 16.1 GB of weights (the file's 17,306,324,000 bytes) + 202 MB of FP16 KV cache + 2.13 GB of compute buffers and runtime (0.5 GB + 10%) = 18.4 GB.
Badge for your model card
Paste it into a Hugging Face or GitHub README; it shows the Q4_K_M total above and links to this page. Q8_0 and FP16 badges.
Numbers read from the model files on Hugging Face on . Compare it with other models in the reproducible model and GPU report.