06 / Tools

Will it fit?

Choose your model and cards to estimate memory use, then compare the result with measured recipes.

Go to the calculator ยท How the numbers work

The calculator needs JavaScript. The model presets, the formulas, the memory per card and what every recipe measured are below, so the sums can be done by hand.

Model presets

One preset for each model family the wiki's recipes use. Architecture numbers are read from each model's config.json on Hugging Face and parameter counts from the checkpoint's tensor shapes; none of the configs is gated.

Model presets, read from each model's config.json
ModelLayersHiddenHeads (KV)Head dimVocabParametersExpertsKV cache per token, 16-bitFixed per userContext in config
DeepSeek V4 Flashdeepseek-ai/DeepSeek-V4-Flash-0731, config.json read 2026-11-03 (revision 7872f01b1d)MoE, 43 compressed-attention layers (2 window only, 21 at ratio 4, 20 at ratio 128)434,09664 (1)512129,280284.3B text model, 13.80B activeplus 19.85B draft layers256 routed, 6 per token, 1 shared6.72 KiB5.4 MiB window1,048,576
DeepSeek V4.1 Flashdeepseek-ai/DeepSeek-V4.1-Flash-1017, config.json read 2026-11-03 (revision 1bae0e1088)MoE, 40 compressed-attention layers sharing 4 KV source layers, with Engram n-gram tables405,12064 (1)512129,280551.9B text model, 16.79B activeplus 14.23B draft layers, 0.49B encoders, 196.6B n-gram tables384 routed, 6 per token, 1 shared3.13 KiB5.0 MiB window1,048,576
GLM 5.3 Flashzai-org/GLM-5.3-Flash, config.json read 2026-11-03 (revision 46a050bec1)MoE, 34 KDA linear-attention layers and 11 sparse-attention MLA layers454,09664 (64)256154,880313.3B text model, 17.38B activeplus 7.43B draft layers, 0.56B encoders288 routed, 8 per token, 1 shared11.69 KiB140.8 MiB state1,048,576
GLM 5.3zai-org/GLM-5.3, config.json read 2026-11-03 (revision ba32f8c19c)MoE, 78 MLA layers with DeepSeek sparse attention786,14464 (64)192154,880743.4B text model, 41.25B activeplus 9.95B draft layers256 routed, 8 per token, 1 shared93.00 KiBnone1,048,576
GLM 5.2zai-org/GLM-5.2, config.json read 2026-11-03 (revision cf457fa734)MoE, 78 MLA layers with DeepSeek sparse attention786,14464 (64)192154,880743.4B text model, 41.25B activeplus 9.95B draft layers256 routed, 8 per token, 1 shared93.00 KiBnone1,048,576
Qwen3.8 Flash NextQwen/Qwen3.8-Flash-Next, config.json read 2026-11-03 (revision de4b8e4d43)MoE, 12 full-attention layers (2 KV heads x 256) and 36 Gated DeltaNet linear-attention layers482,56024 (2)256248,320125.7B text model, 7.31B activeplus 2.61B draft layers, 0.45B encoders, 51.20B n-gram tables512 routed, 10 per token, 1 shared24.75 KiB110.1 MiB state262,144
Qwen3.6 27BQwen/Qwen3.6-27B, config.json read 2026-11-03 (revision 6a9e13bd6f)16 full-attention layers (4 KV heads x 256) and 48 Gated DeltaNet linear-attention layers645,12024 (4)256248,32026.90B text model, 26.90B activeplus 0.43B draft layers, 0.46B encodersdense64.00 KiB146.8 MiB state262,144
Qwen3.8 27BQwen/Qwen3.8-27B, config.json read 2026-11-03 (revision 1d4bf0f2ff)16 full-attention layers (4 KV heads x 256) and 48 Gated DeltaNet linear-attention layers645,12024 (4)256248,32026.90B text model, 26.90B activeplus 0.43B draft layers, 0.46B encodersdense64.00 KiB146.8 MiB state262,144
MiMo V2.6 FlashXiaomiMiMo/MiMo-V2.6-Flash-RL, config.json read 2026-11-03 (revision f657ba2f7d)MoE, 9 full-attention and 39 sliding-window layers (window 128)484,09664 (4)192152,576308.8B text model, 15.45B activeplus 0.99B draft layers, 0.99B encoders256 routed, 8 per token22.50 KiB24.4 MiB window1,048,576
Mistral Large 4mistralai/Mistral-Large-4-1T-A52B, config.json read 2026-11-03 (revision af26e7869a)MoE, 72 MLA layers with an indexer (63 own a KV cache)726,14464 (64)64204,8001.05T text model, 52.34B activeplus 2.10B draft layers, 1.70B encoders128 routed, 4 per token, 1 shared81.88 KiBnone1,048,576
Laguna-S-2.1poolside/Laguna-S-2.1, config.json read 2026-11-03 (revision 0f57314083)MoE, 12 full-attention and 36 sliding-window layers (window 512)483,07248 (8)128100,352117.6B text model, 8.45B active256 routed, 10 per token, 1 shared48.00 KiB72.0 MiB window1,048,576

How the numbers are made

Every number on this page carries one of three labels. Measured: a recipe or an owner on the wiki reported it. Calculated: the formulas below applied to the model's config.json. Assumed: an allowance the configs and the wiki do not give, stated so you can change it.

  1. Weights: bytes = parameters x bits per weight / 8. Counted in parts so each can have its own bits: routed experts; attention, shared experts and dense layers; embeddings and output head (16 bits by default, the way most quants leave them); draft layers (MTP or DSpark) and encoders when included (encoders at 16 bits). For a MoE model every expert is held in memory: total parameters set the memory, active parameters set the speed.
  2. KV cache per token: 2 x layers x KV heads x head_dim x bytes. Bytes per value: 2 for FP16 or BF16, 1 for FP8 or Q8, 0.5 for Q4. When K and V have different sizes the sum K + V replaces 2 x head_dim. Only layers that keep a cache count: hybrid models count their full-attention layers.
  3. MLA cache per token: layers x (kv_lora_rank + qk_rope_head_dim) x bytes. Multi-head latent attention caches one latent per layer instead of K and V per head (GLM 5.2, GLM 5.3, the sparse-attention layers of GLM 5.3 Flash, Mistral Large 4). Sparse-attention indexers add their own keys: layers with an indexer x index_head_dim x bytes.
  4. DeepSeek V4 and V4.1 cache per token: layers x head_dim / compress ratio x bytes, plus a window. Their configs have no kv_lora_rank: each entry is one head_dim (512) latent for K and V together, and a layer stores one entry per compress_ratios tokens, plus the last sliding_window (128) tokens raw. V4.1 keeps the long-range cache only on its kv_source_layer_ids and shares it. Indexer keys: index_head_dim / ratio on the layers that own them.
  5. Sliding-window layers: layers x per-token size x min(context, window). A sliding-window layer never holds more than its window, whatever the context (MiMo V2.6 Flash, Laguna-S-2.1, the DeepSeek V4 windows).
  6. Linear-attention state: layers x heads x key dim x value dim x bytes, per user. Gated DeltaNet (Qwen3.6, Qwen3.8) and KDA (GLM 5.3 Flash) layers keep a fixed state per sequence instead of a cache that grows, plus a small convolution state.
  7. Total KV: per token x context x concurrent users, plus window and state x users. Every user is assumed to fill the full context. Engines with a shared KV pool (vLLM, SGLang, llama.cpp with slots) let users share a pool, so the same pool serves more users at shorter contexts.
  8. Fit: weights + KV + state + overhead x cards against cards x usable memory per card. Fits at or under 95% of usable memory, tight from 95% to 100%, does not fit above. An even split across cards is assumed; pipeline ranks are uneven (the last rank holds the output head and often the drafter), so leave room on one card.

Memory is in GiB (1,073,741,824 bytes), the unit the unlock sizes are in (64 GB = 65,536 MiB). Parameters are counted from the tensor shapes in each checkpoint, so draft layers, encoders and n-gram tables can be left out or kept off the cards.

Memory per card

  • 8 GB card at 64 GB: 63.39 GiB usable (Measured). 64,911 MiB (63.39 GiB) usable of the 65,536 MiB unlock, as the recipe DeepSeek V4.1 Flash on 4x 8 GB (alanoo fidelity build) reports it. The top of VRAM backs the GSP firmware: tail-reserve unlocker forks expose 65,344 MiB or 64,768 MiB, and on builds without the late-PMA fix cuda_memtest passes only when capped at about 63.75 GB. Filling a card into that tail crashes it. Source: Xid 31 and the reserved top of VRAM.
  • 10 GB card at 40 GB: 37.50 GiB usable (Measured). The wiki says to plan for about 37 to 38 GiB usable of the 40 GB profile after reservations (one owner measured about 37.7 GiB per card on four cards); the middle, 37.5 GiB, is used. A model that goes over the cap crashes the card and needs a restart. Source: Memory unlock on the 10 GB card.
  • 10 GB card at 48 GB: 45.50 GiB usable (Assumed). The wiki gives no usable figure for 48 GB, which needs a good sixth HBM stack (about one card in five). The same 2.5 GiB reservation as the 40 GB profile is assumed: 45.5 GiB. No recipe was measured at 48 GB. Source: Memory unlock on the 10 GB card.
  • Overhead: CUDA context, engine workspace, activations and graphs: 1.5 GiB per card is assumed. Engines that take a share of memory (vLLM --gpu-memory-utilization, SGLang --mem-fraction-static) leave the rest outside their pool; where a recipe states its share, the page shows what it left free. (Assumed)

Where each cache size comes from

DeepSeek V4 Flash
  • Compressed latent, ratio 4 layers: 21 layers (compress_ratios 4) x 512 head_dim / 4
  • Compressed latent, ratio 128 layers: 20 layers (compress_ratios 128) x 512 head_dim / 128
  • Indexer keys, ratio 4 layers: 21 layers x 128 index_head_dim / 4
  • Sliding window, every layer: 43 layers x 512 head_dim, at most 128 tokens (sliding_window)
  • No kv_lora_rank in this config: each layer caches one 512-value latent (head_dim 512, num_key_value_heads 1, of which qk_rope_head_dim 64 carry position) for K and V together. Layers store one latent per compress_ratios tokens plus a 128-token window, as the reference inference/model.py allocates them.
DeepSeek V4.1 Flash
  • Compressed latent, KV source layers at ratio 2: 3 layers (kv_source_layer_ids 2, 8, 14) x 512 head_dim / 2
  • Compressed latent, KV source layers at ratio 1: 1 layers (kv_source_layer_ids 20) x 512 head_dim / 1
  • Indexer keys at ratio 2: 3 layers that own index keys (in both kv_source_layer_ids and index_source_layer_ids) x 128 index_head_dim / 2
  • Indexer keys at ratio 1: 1 layers that own index keys (in both kv_source_layer_ids and index_source_layer_ids) x 128 index_head_dim / 1
  • Sliding window, every layer: 40 layers x 512 head_dim, at most 128 tokens (sliding_window)
  • Only the 4 layers in kv_source_layer_ids keep a long-range cache; the other layers read theirs. No kv_lora_rank in this config: each entry is one 512-value latent (head_dim) for K and V together, as the reference inference/model.py allocates it.
  • The Engram n-gram tables (2 layers, 384,006,168 and 384,016,682 rows x 256 engram_head_dim, stored FP8 with one scale per 32 values) are counted on their own: most recipes keep them off the cards.
GLM 5.3 Flash
  • MLA latent, sparse-attention layers: 11 layers (layer_types deepseek_sparse_attention) x (512 kv_lora_rank + 0 qk_rope_head_dim)
  • Indexer keys, sparse-attention layers: 11 layers x 128 index_head_dim / 4 index_kpool
  • Recurrent state, KDA linear-attention layers: 34 layers (kda_layers) x 64 heads x 128 x 128 x 4 bytes (Assumed: the config does not state the state dtype; 4 bytes (fp32) is assumed)
  • Convolution state, KDA layers: 34 layers x (4 short_conv_kernel_size - 1) x 3 (q, k, v) x 64 x 128 channels x 2 bytes (Assumed: 2 bytes (the checkpoint dtype) is assumed for the convolution state)
GLM 5.3
  • MLA latent, every layer: 78 layers x (512 kv_lora_rank + 64 qk_rope_head_dim)
  • Sparse-attention indexer keys: 21 layers with their own indexer (indexer_types full) x 128 index_head_dim
GLM 5.2
  • MLA latent, every layer: 78 layers x (512 kv_lora_rank + 64 qk_rope_head_dim)
  • Sparse-attention indexer keys: 21 layers with their own indexer (indexer_types full) x 128 index_head_dim
Qwen3.8 Flash Next
  • K and V, full-attention layers: 2 x 12 layers (layer_types full_attention) x 2 KV heads x 256 head_dim
  • Indexer keys, full-attention layers: 12 layers x 1 indexer_kv_heads x 128 indexer_head_dim / 4 indexer_compress_ratio
  • Recurrent state, linear-attention layers: 36 layers (layer_types linear_attention) x 48 linear_num_value_heads x 128 x 128 x 4 bytes (mamba_ssm_dtype float32)
  • Convolution state, linear-attention layers: 36 layers x (4 linear_conv_kernel_dim - 1) x (2 x 16 x 128 + 48 x 128) channels x 2 bytes (Assumed: 2 bytes (the checkpoint dtype) is assumed for the convolution state)
  • The per-layer n-gram embedding table (PLE, ngram_vocab_size_base 20,000,000 x ple_embed_dim 2560) is counted on its own: most recipes keep it in host RAM or on an SSD.
Qwen3.6 27B
  • K and V, full-attention layers: 2 x 16 layers (layer_types full_attention) x 4 KV heads x 256 head_dim
  • Recurrent state, linear-attention layers: 48 layers (layer_types linear_attention) x 48 linear_num_value_heads x 128 x 128 x 4 bytes (mamba_ssm_dtype float32)
  • Convolution state, linear-attention layers: 48 layers x (4 linear_conv_kernel_dim - 1) x (2 x 16 x 128 + 48 x 128) channels x 2 bytes (Assumed: 2 bytes (the checkpoint dtype) is assumed for the convolution state)
Qwen3.8 27B
  • K and V, full-attention layers: 2 x 16 layers (layer_types full_attention) x 4 KV heads x 256 head_dim
  • Recurrent state, linear-attention layers: 48 layers (layer_types linear_attention) x 48 linear_num_value_heads x 128 x 128 x 4 bytes (mamba_ssm_dtype float32)
  • Convolution state, linear-attention layers: 48 layers x (4 linear_conv_kernel_dim - 1) x (2 x 16 x 128 + 48 x 128) channels x 2 bytes (Assumed: 2 bytes (the checkpoint dtype) is assumed for the convolution state)
MiMo V2.6 Flash
  • K and V, full-attention layers: 9 layers (hybrid_layer_pattern 0) x 4 KV heads x (192 head_dim + 128 v_head_dim)
  • K and V, sliding-window layers: 39 layers (hybrid_layer_pattern 1) x 8 swa_num_key_value_heads x (192 + 128), at most 128 tokens
Mistral Large 4
  • MLA latent, layers that own a cache: 63 layers (distinct kv_source_layers) x (512 kv_lora_rank + 64 qk_rope_head_dim)
  • Sparse-attention indexer keys: 44 layers (indexer_types full) x 128 index_head_dim
  • 9 of the 72 layers read the KV cache of layer 35 (kv_source_layers), so 63 layers hold one.
Laguna-S-2.1
  • K and V, full-attention layers: 2 x 12 layers (layer_types full_attention) x 8 KV heads x 128 head_dim
  • K and V, sliding-window layers: 2 x 36 layers (layer_types sliding_attention) x 8 x 128, at most 512 tokens (sliding_window)

The formula against the recipes

What the formula gives at a recipe's own setup, next to what the recipe reports. The gap is what the formula leaves out: engine pools sized by a memory share, quant mixes and runtime buffers.

  • GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 layer split): Weights plus KV cache, both cards: Calculated 113.6 GiB, Measured 116.6 GiB; the formula comes out 2.6% under. EXL3 3.05 bpw on every layer, Q8 KV at 392,960 tokens (profile q8_384k), no draft layers or encoders; measured: 116.6 GiB resident across both.
  • MiMo V2.6 Flash on 4x 8 GB: Weights, four cards: Calculated 165.3 GiB, Measured 182.0 GiB; the formula comes out 9.2% under. NVFP4 at 4.5 bits on every layer, embeddings and encoders 16-bit; measured: 45.5 GiB of weights per card. The checkpoint is a ModelOpt mixed-precision NVFP4, so some layers are above 4.5 bits.
  • DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8): Weights, eight ranks: Calculated 285.8 GiB, Measured 299.3 GiB; the formula comes out 4.5% under. MXFP4 experts, 8-bit dense, DSpark layers in, Engram tables off the cards; measured: 35.9 per rank for ranks 1 to 6, 37.6 rank 0, 46.3 rank 7 (posted as GB, compared as GiB).
  • DeepSeek V4 Flash 0731 on 3x 8 GB (PP3 DSpark): Weights against the official checkpoint size: Calculated 154.7 GiB, Measured 155.4 GiB; the formula comes out 0.5% under. MXFP4 experts, FP8 attention, BF16 embeddings, DSpark layers in; measured: about 155.4 GiB (the checkpoint as stated in the recipe).
  • Qwen3.8 Flash Next on 2x 8 GB (vektorprime PP2): Weights, two ranks: Calculated 64.2 GiB, Measured 85.0 GiB; the formula comes out 24.4% under. AWQ INT4 at 4.125 bits, embeddings 16-bit, MTP layers in, PLE table in host RAM; measured: 39.48 and 45.53 GiB of weights on the two ranks.
  • Mistral Large 4 on 8x 8 GB (llama.cpp lab trial): Weights against the file size: Calculated 374.1 GiB, Measured 394.0 GiB; the formula comes out 5.0% under. IQ3_XXS at 3.0625 bits on every tensor; measured: the UD-IQ3_XXS files are 394 GiB, because the mix keeps some tensors above IQ3_XXS.
  • Qwen3.6 27B on 1x 10 GB (llama.cpp MTP): Weights plus a 4,096-token cache, Q4: Calculated 15,058 MiB, Measured 17,464 MiB; the formula comes out 13.8% under. Q4_K at 4.5 bits on every tensor, MTP layer in, no overhead; measured: 17,464 MiB used at UD-Q4_K_XL (context not stated).
  • Qwen3.6 27B on 1x 10 GB (llama.cpp MTP): Weights plus a 4,096-token cache, Q8: Calculated 28,086 MiB, Measured 35,718 MiB; the formula comes out 21.4% under. Q8_0 at 8.5 bits; measured: 35,718 MiB used at UD-Q8_K_XL.
  • Qwen3.6 27B on 1x 10 GB (SGLang W8A8): Largest context at one user: Calculated 117,748 tokens, Measured 24,576 tokens; the formula allows 4.8 times the recipe's context. W8A8 at 8 bits, 16-bit KV, 37.5 GiB usable, 1.5 GiB overhead; measured: a 24,576-token pool. SGLang sizes its pool from a static memory share and the recipe also runs an EAGLE draft, so the pool is far below what the memory allows.
  • DeepSeek V4 Flash 0731 on 3x 8 GB (PP3 DSpark): Largest context at one user: Calculated 9,673,868 tokens, Measured 691,968 tokens; the formula allows 14.0 times the recipe's context. The cache is about 3.4 KB per token, so memory allows far more than 1M; the recipe's 691,968 was the largest stable context at utilization 0.965, limited by transient buffers that grow with context (Xid 31 page), not by the cache.

Not counted: draft models that ship separately (DFlash2 drafters), the KV cache of draft layers, the DeepSeek compressor's small per-user buffers, and engine-specific cache layouts (some 8-bit caches keep scales and the position part at 16 bits, so they run larger).

What the recipes measured

What each recipe measured
RecipeCardsQuantContext tokensVRAM per card, as postedUsers
DeepSeek V4 Flash pruned on 4x 10 GBDeepSeek V4 Flash4 x 10 GBnot statednot statedabout 37 GB usable per card (40 GB profile), 148 GB in totalnot stated
DeepSeek V4 Flash 0731 on 3x 8 GB (PP3 DSpark)DeepSeek V4 Flash3 x 8 GBNative MXFP4 experts + FP8 attention (official deepseek-ai checkpoint, about 155.4 GiB); KV cache fp8691,96864 GB (65,536 MiB), --gpu-memory-utilization 0.965not stated
DeepSeek V4 Flash 0731 on 4x 8 GB (allover326 PP4 DSpark)DeepSeek V4 Flash4 x 8 GBNative MXFP4 experts + FP8 attention (official deepseek-ai checkpoint, about 155.4 GiB); KV cache fp81,047,73664 GB, --gpu-memory-utilization 0.8564
DeepSeek V4.1 Flash on 2x 8 GB (Project Maya)DeepSeek V4.1 Flash2 x 8 GBGSQ-RCO 2-bit GGUF (this row); Maya GGUF (Maya-S 340 GB or Maya-XS 277 GB; Engram tables stay on SSD)not stated64 GBnot stated
DeepSeek V4.1 Flash heretic on 4x 8 GBDeepSeek V4.1 Flash4 x 8 GBHybrid: routed experts EXL3 2.9 bpw (LibertAIDAI), everything else official FP8/BF16 with the 38 heretic attn.wo_b tensors262,14464 GiB, --gpu-memory-utilization 0.92 (miner co-resident)8
DeepSeek V4.1 Flash on 4x 8 GB (alanoo fidelity build)DeepSeek V4.1 Flash4 x 8 GBHybrid: all 40 expert layers at 3 bits (LibertAI 2.9 bpw pack with layers 18-22 grafted from the 3.5 bpw pack), official FP8 dense tensors262,14464 GiB (64,911 MiB usable), GPU_MEMORY_UTILIZATION 0.988
DeepSeek V4.1 Flash on 4x 8 GB (CurtisAccelerate TC-MoE)DeepSeek V4.1 Flash4 x 8 GBHybrid: LibertAI EXL3 2.9 bpw routed experts (layers 0-39), official FP8/FP4 for attention, shared experts, head, draft and Engram; KV fp8_ds_mla262,144about 62.5 GB used of 64 GB, --gpu-memory-utilization 0.978
DeepSeek V4.1 Flash on 4x 8 GB (GNmac with copy fix and faster prefill)DeepSeek V4.1 Flash4 x 8 GBHybrid as recipe 1.2.0: routed experts EXL3 from LibertAI's 2.9 bpw pack (mostly 3 bpw, 2 bpw on layers 18-22); attention, shared experts, indexer and DSpark drafter official FP8; KV fp8_ds_mla262,14464 GiB, GPU_MEMORY_UTILIZATION 0.958
DeepSeek V4.1 Flash on 4x 8 GB (GNmac)DeepSeek V4.1 Flash4 x 8 GBHybrid: routed experts EXL3 (mostly 3 bpw, 2 bpw on layers 18-22) from LibertAI's 2.9 bpw pack; attention, shared experts, indexer and DSpark drafter official FP8; KV fp8_ds_mla262,14464 GiB, GPU_MEMORY_UTILIZATION 0.958
DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)DeepSeek V4.1 Flash4 x 8 GBHybrid: routed experts EXL3 2.9 bpw (LibertAIDAI), everything else official FP8/BF16; KV BF16262,14464 GiB exposed, --gpu-memory-utilization 0.95 (fixed by the release since 1.0.1)8
DeepSeek V4.1 Flash on 4x 8 GB plus RTX PRO 6000 (ExLlamaV3 TP5)DeepSeek V4.1 Flash4 x 8 GBEXL3 3.5 bpw (LibertAIDAI; routed experts 4 bpw on layers 0-9 and 30-39, 3 bpw on 10-29; attention and shared experts 6 bpw) plus the official Engram shards1,048,576gpu_split 58 GB per CMP, 70 GB on the PROnot stated
DeepSeek V4.1 Flash on 5x 8 GB (PP5 full residency)DeepSeek V4.1 Flash5 x 8 GBOfficial checkpoint (510 GB: MXFP4 routed experts, FP8 dense layers, 203 GB FP8 Engram table); KV cache fp8_ds_mla1,048,57664 GB, full residency (no expert offload), --gpu-memory-utilization 0.97not stated
DeepSeek V4.1 Flash on 6x 8 GB (Deepinfer-SM80 TP2 x PP3)DeepSeek V4.1 Flash6 x 8 GBOfficial checkpoint (FP8 dense, FP4 experts); software FP8 on sm_801,048,57664 GiBnot stated
DeepSeek V4.1 Flash on 6x 8 GB (TP6)DeepSeek V4.1 Flash6 x 8 GBOfficial checkpoint: dense MXFP8 through an SM80 Marlin W8A16 path, routed experts MXFP4 through W4A16; KV FP81,048,57664 GB, --gpu-memory-utilization 0.95not stated
DeepSeek V4.1 Flash on 8x 8 GB (Deepinfer-SM80 TP4 x PP2)DeepSeek V4.1 Flash8 x 8 GBOfficial checkpoint (FP8 dense, FP4 experts); software FP8 on sm_801,048,57664 GiB, --gpu-memory-utilization 0.9512
DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)DeepSeek V4.1 Flash8 x 8 GBOfficial checkpoint as downloaded: MXFP4 routed experts as Marlin W4A16, MXFP8 dense as Marlin W8A16; KV fp81,048,57664 GB; weights 35.9 GB per rank (ranks 1-6), 37.6 GB rank 0, 46.3 GB rank 78
GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 layer split)GLM 5.3 Flash2 x 8 GBEXL3 3.05 bpw: turboderp/GLM-5.3-Flash-exl3392,960about 58 GiB of 64 GiB (116.6 GiB resident across both)not stated
GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2)GLM 5.3 Flash2 x 8 GBEXL3 3.05 bpw: turboderp/GLM-5.3-Flash-exl3; DFlash2 drafter converted to EXL3 6 bpw392,960about 62.9 / 62.3 GiB idle, peaks about 64.4 / 63.0 GiB with vision2
GLM 5.3 Flash on 2x 8 GB (Project Maya)GLM 5.3 Flash2 x 8 GBMaya-M GGUF (116 GB), every expert in VRAM; Maya-S (96.5 GB) and Maya-S24 (94.7 GB) also reportednot stated64 GBnot stated
GLM 5.3 Flash on 3x 8 GBGLM 5.3 Flash3 x 8 GBW4A16, about 4.3 bpw, 163 GiB on disknot stated64 GiBnot stated
GLM 5.3 Flash on 4x 8 GBGLM 5.3 Flash4 x 8 GBW4A16 (INT4 weights, group size 128, FP16 activations): canada-quant/GLM-5.3-Flash-W4A16-MTP262,14464 GiB exposed, --gpu-memory-utilization 0.958
GLM 5.3 Flash on 4x 8 GB (kaka86mm EXL3 + Marlin sidecar + DFlash2)GLM 5.3 Flash4 x 8 GBEXL3 4 bpw (Mia-AiLab/GLM-5.3-Flash-EXL3-TR3-4bpw, 164 GB) plus an offline-generated Marlin INT4 decode sidecar (151 GB)524,28864 GB, --gpu-memory-utilization 0.93 (0.94 is the ceiling)4
GLM 5.3 Flash on 8x 8 GB (promisezackr PP8 NVFP4 DFlash2)GLM 5.3 Flash8 x 8 GBLibertAIDAI/GLM-5.3-Flash-NVFP4 (ModelOpt NVFP4, routed experts only, 181 GiB), run through Marlin W4A16 kernels; GLM-5.3-Flash DFlash2 drafter (5 sliding-window layers)1,048,57664 GB, --gpu-memory-utilization 0.9016
GLM 5.3 on 8x 8 GB (cebeuq glm53-cmp170hx-recipe)GLM 5.38 x 8 GBhybrid: the published NVFP4 routed experts unchanged plus an INT8-g128 residue, converted offline from dealignai/GLM-5.3-ABLITERATED-NVFP4 (432.9 GiB source)524,28864 GB (65,536 MiB), GPU memory utilization 0.978
GLM 5.3 on 8x 8 GB (Int4-Int8Mix PP8)GLM 5.38 x 8 GBGLM-5.3-Int4-Int8Mix (INT4 / INT8 mix); KV fp8_ds_mla1,048,57664 GiB, --gpu-memory-utilization 0.97not stated
GLM 5.3 on 8x 8 GB (vllm-170hx-glm5)GLM 5.38 x 8 GBGLM-5.3-Int4-Int8Mix-AWQ-g64; drafter incoai/GLM-5.3-DFlash21,048,57664 GiB, GPU_UTIL 0.96 at PP88
GLM 5.3 on 8x 8 GB plus 2x RTX PRO 6000 (vLLM TP2 x PP5)GLM 5.38 x 8 GBcebeuq's hybrid: the published NVFP4 routed experts unchanged plus an INT8-g128 residue, converted from dealignai/GLM-5.3-ABLITERATED-NVFP4; about 420 GB on disk524,28864 GB unlocked; per CMP about 32.5 GiB loaded and 28.6 GiB for KV (last pair 43.7 and 17.3)8
GLM 5.2 on 3x 10 GB (llama.cpp CPU offload)GLM 5.23 x 10 GBQ4 GGUF (the exact Q4 file is not named); UD-Q2_K_XL also testednot stated40 GB profile (10 GB card unlocked to 40 GB)not stated
GLM 5.2 on 8x 8 GBGLM 5.28 x 8 GB4-bit, posted as int4 and q4 (the checkpoint is named in Notes)not stated64 GB (8 GB card unlocked)not stated
Qwen3.8 Flash Next on 1x 8 GB (ElectroHobo 3 bpw)Qwen3.8 Flash Next1 x 8 GBAutoRound mixed 2/3-bit (klee100, 2.998 effective bpw, 47 GiB on card) plus halt95's FP8 n-gram table in host RAM262,14464 GiB, --gpu-memory-utilization 0.95 (fixed)48
Qwen3.8 Flash Next on 1x 8 GB (iIIusi0n SSD PLE)Qwen3.8 Flash Next1 x 8 GBAutoRound 3 bpw + MTP: klee100/Qwen3.8-Flash-Next-AutoRound-3bpw-MTP; 95.37 GiB BF16 PLE table on SSD262,14464 GiB, --gpu-memory-utilization 0.9616
Qwen3.8 Flash Next on 2x 8 GB (DUFRelic PP2)Qwen3.8 Flash Next2 x 8 GBW4A16 INT4 g128 with the PLE table repacked INT4 g32: zankich/Qwen3.8-Flash-Next-W4A16-Merlin-INT4PLE-FP8KV; KV BF16262,14464 GiB, --gpu-memory-utilization 0.904
Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)Qwen3.8 Flash Next2 x 8 GBW4A16: halt95/Qwen3.8-Flash-Next-W4A16-Merlin (AutoRound INT4 g128 experts, INT8 GDN projections, FP8 n-gram table)262,14464 GiB, GPU_UTIL 0.95 (fixed)128
Qwen3.8 Flash Next on 2x 8 GB (mannydelrio PP2)Qwen3.8 Flash Next2 x 8 GBAWQ W4A16 g32 (leoncca/Qwen3.8-Flash-Next-Uncensored-AWQ-g32); PLE table converted to INT4 and served from SSD262,14464 GB, --gpu-memory-utilization 0.94, TB_TORCH_MEM_CAP_GIB=61.58
Qwen3.8 Flash Next on 2x 8 GB (Morrowmake EXL3)Qwen3.8 Flash Next2 x 8 GBEXL3 5.05 bpw; PLE (n-gram) table read from SSD262,14464 GiB, --gpu-memory-utilization 0.958
Qwen3.8 Flash Next on 2x 8 GB (Plean PP2)Qwen3.8 Flash Next2 x 8 GBMixed INT4 AutoRound (Minachist/Qwen3.8-Flash-Next-INT4-Mixed-AutoRound, about 65 GB) with the full BF16 PLE table on NVMe262,14464 GBnot stated
Qwen3.8 Flash Next on 2x 8 GB (Qwen-Flash-SM80, GDS TEP2)Qwen3.8 Flash Next2 x 8 GBNVFP4 main weights through Marlin (no native FP4 on sm_80), mixed FP8 and BF16 MTP weights, FP8 PLE table (about 51.2 GB) kept on NVMe262,14464 GB, --gpu-memory-utilization 0.93 (v0.3.0)10
Qwen3.8 Flash Next on 2x 8 GB (vektorprime PP2)Qwen3.8 Flash Next2 x 8 GBAWQ INT4: cyankiwi/Qwen3.8-Flash-Next-AWQ-INT4; 95 GiB BF16 PLE table in host RAM (FP8 table optional)262,14464 GiB; weights PP0 39.48 GiB, PP1 45.53 GiB; --gpu-memory-utilization 0.9not stated
Qwen3.8 Flash Next on 3x 8 GB (clee PP3)Qwen3.8 Flash Next3 x 8 GBW4A16 AutoRound: Intel/Qwen3.8-Flash-Next-W4A16-AutoRound; 95.4 GiB BF16 PLE table streamed from NVMe; KV fp8 e4m3 (software-decoded on SM80)1,048,57664 GiB, gpu-memory-utilization 0.92not stated
Qwen3.8 Flash Next on 3x or 4x 8 GB (zebgop-ops FP8 PP)Qwen3.8 Flash Next4 x 8 GBOfficial block FP8, about 126 GiB including the about 50 GiB FP8 n-gram (PLE) table, which is served from host RAM; KV cache bf16 (the QSA layers refuse fp8)262,14464 GiB; --gpu-memory-utilization 0.94 plus per-rank KV budgets; measured 34.0-34.3 GiB per 12-layer rank, 37.9 GiB on the drafter rank8
Qwen3.8 Flash Next on 4x 8 GBQwen3.8 Flash Next4 x 8 GBAWQ W4A16: wtdcode/Qwen3.8-Flash-Next-AWQ-W4A161,000,00064 GBnot stated
Qwen3.6 27B on 1x 10 GB (llama.cpp MTP)Qwen3.6 27B1 x 10 GBUD-Q4_K_XL GGUF (UD-Q8_K_XL also tested)not stated40 GB profile; 17,464 MiB used at Q4, 35,718 MiB at Q8not stated
Qwen3.6 27B on 1x 10 GB (SGLang W8A8)Qwen3.6 27B1 x 10 GBINT8 W8A8 (compressed-tensors, dynamic)24,57640 GiB profile (40,960 MiB)4
Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)Qwen3.8 27B1 x 8 GBW4A16 (INT4 weights, Marlin kernels)262,14464 GBnot stated
MiMo V2.6 Flash on 4x 8 GBMiMo V2.6 Flash4 x 8 GBNVFP4 (ModelOpt mixed precision): ProCreations/MiMo-V2.6-Flash-RL-NVFP4, run as 4-bit weights with BF16 activations through Marlin1,048,57664 GiB; weights 45.5 GiB plus 10 GiB KV per card; GPU_UTIL 0.94 (fixed)8
Mistral Large 4 on 8x 8 GB (llama.cpp lab trial)Mistral Large 48 x 8 GBunsloth UD-IQ3_XXS GGUF (394 GiB in 10 files); DSpark drafter Q8_0 (2.1 GB)196,60854 to 63 GiB of 64 used8
Laguna-S-2.1 on 2x 10 GBLaguna-S-2.12 x 10 GBNVFP4 GGUF (runs through a fallback path: the cards have no native FP4)131,072not statednot stated

The same recipes by setup: Setup matrix; on the wiki: All recipes and Recipe finder. 47 recipes read from the wiki's Recipe table at 2026-11-11 23:08 UTC; refreshed every 10 minutes.

About this calculator and its sources

Pick a model, a quant, a context length, how many users at once and your cards, and this page works out whether the weights and the KV cache fit, with every step of the arithmetic shown. Architecture numbers come from each model's config.json; card memory comes from the wiki. Where a recipe ran the same model on the same card, its measured VRAM and context sit next to the result, so you can see how far the formula is from a real run.