archdb

LLM architectures and pretraining recipes, with sources.

Laguna-XS.2

Poolside · reasoning checkpoint

No base checkpoint is public; facts describe the released post-trained checkpoint.

Open in the comparison table Hugging Face ↗ Paper ↗

KV calculations use one sequence at 131,072 tokens and 16-bit cache elements. They include bounded sliding-window caches. This is retained cache payload, not peak prefill memory. The comparison table also offers sourced mixed-precision layouts, including quantization scales.

Release

Released

2026-04-28

Source: blog · Introducing Laguna XS.2 and Laguna M.1; post date and Get started
category:"announcements",date:"2026-04-28"

Same post: "Weights are live today under Apache 2.0."

Date the weights (or, if earlier, the technical report) were first made public, YYYY-MM-DD, as dated by the publisher. A Hugging Face repository creation date is used only when no dated publisher page exists, with a note.

License

apache-2.0

Source: model-card · README.md; YAML front matter
license: apache-2.0

License of the released weights as declared by the publisher (model card metadata or license file), e.g. apache-2.0, mit, or the name of a custom license.

Input modalities

text

Source: model-card · Model overview
Modality: text-to-text

Input modalities of the released checkpoint as the publisher states them, from: text, image, video, audio, joined with ' + ' in that order ("text", "text + image + video").

Parameters

Total params

33.4B parameters

Source: paper · p.5 §3.1 Architecture & Training
LAGUNA XS.2 has a total parameter count of 33.4B

Total parameter count as reported by the publisher. See params.note for whether embeddings, MTP heads or vision towers are included.

Active params

3B parameters

Source: paper · p.5 §3.1 Architecture & Training
with 3B parameters (including embeddings) activated per token

Parameters used per token in the forward pass, as reported by the publisher.

Active non-embedding (stated)

2.59B parameters

Inferred from the source; see the explanation below.

Source: paper · p.5 §3.1 Architecture & Training
with 3B parameters (including embeddings) activated per token

~3B − 2 × 100,352 × 2,048 (input embedding and untied LM head) = ~2.59B.

Active parameters excluding the input embedding and the output head (unembedding). Stated by the publisher, or computed from params.active by subtracting vocab × d_model for each of the embedding and output head that params.active is stated to include (basis inferred, note with the arithmetic). Not disclosed when the scope of params.active is not stated.

Counted total params

33.44B parameters

Calculated: embedding + output head + all experts + other weights, poolside/Laguna-XS.2@a397bde safetensors headers; reproduces stated total (backbone) and active (with embedding and output head)

Parameters of the text backbone counted from the released checkpoint's safetensors headers (embedding, output head, all experts and other weights; excluding MTP modules, vision/audio towers and n-gram lookup tables). Shown only when the counts reproduce the publisher's stated total and active parameters within 5% under some scope.

Counted embedding + head

411M parameters

Calculated: input embedding + output head, poolside/Laguna-XS.2@a397bde safetensors headers

Input embedding plus output head (once if tied), counted from the checkpoint.

Non-emb. params (counted)

33.03B parameters

Calculated: dense + routed backbone weights; excludes input embedding, output head, lookup tables, MTP and other modalities, poolside/Laguna-XS.2@a397bde safetensors headers; reproduces stated total (backbone) and active (with embedding and output head)

Language backbone weights excluding input embeddings, output head, lookup/Engram tables, MTP modules and vision/audio towers. Equals params.counted_total minus params.counted_embedding. Same validation as params.counted_total.

Largest layer (counted)

846.9M parameters

Calculated: max(sum of dense and routed weights sharing a full layers.<index> tensor path), all experts included, poolside/Laguna-XS.2@a397bde safetensors headers

Largest group of language-backbone weights sharing a full layers.<index> tensor path, including every routed expert. Excludes lookup/Engram tables, embeddings, output head, MTP and other modalities. Hybrid checkpoints may store mixers and FFNs as separate layers. All-gather volume also depends on wrapping, sharding and dtype.

Active non-emb. (counted)

2.606B parameters

Calculated: non-expert weights + routed experts × 8/256, excluding embedding and output head, poolside/Laguna-XS.2@a397bde safetensors headers; reproduces stated total (backbone) and active (with embedding and output head)

Active parameters per token excluding the input embedding and output head, counted from the checkpoint as all non-expert weights plus routed-expert weights × top_k / experts. Same validation as params.counted_total.

Counting scope

Active count includes embeddings.

Source: paper · p.5 §3.1 Architecture & Training
with 3B parameters (including embeddings) activated per token

What the publisher's counts include or exclude (MTP modules, embeddings, vision encoder, n-gram tables).

Shape

Layers

40

Source: config · /num_hidden_layers

Number of transformer blocks in the main backbone (attention or token mixer plus FFN), excluding MTP modules.

d_model

2,048

Source: config · /hidden_size

Residual stream width.

Vocab

100,352

Source: config · /vocab_size

Embedding table rows (vocab_size in config, may include padding).

Tied embeddings

No

Source: config · /tie_word_embeddings

Input embedding and output head share weights.

Tokenizer

BPE trained on internal data; shared with M.1

Source: paper · p.5 §3.1
Both models share the same tokenizer with a vocabulary size of 100,352 tokens, trained with Byte-Pair Encoding [75] on our internal datasets.

Tokenizer type and lineage as described by the publisher (e.g. byte-level BPE shared with an earlier model).

d_model / layers

51.2

Calculated: d_model / layers

Width-to-depth ratio, d_model divided by the number of blocks.

Attention

Token mixers

GQA, SWA

Source: paper · p.5 §3.1
In both types of layers, we use Grouped Query Attention (GQA)

Token-mixing layer types in the backbone, e.g. GQA, MLA, SWA, Gated DeltaNet, Mamba-2, DSA (DeepSeek sparse attention).

Layer layout

1 global : 3 SWA

Inferred from the source; see the explanation below.

Source: config · config.json; /layer_types
"layer_types": [ "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention", "full_attention", "sliding_attention", "sliding_attention", "sliding_attention" ]

The pinned /layer_types array repeats this four-layer pattern 10 times, beginning with the global layer. Ordered 40-layer backbone from /layer_types; auxiliary modules are excluded.

Token-mixer order, summarized as a pattern or layer positions. The fact's optional sequence lists each mixer in order; a ratio alone does not establish the order. Auxiliary prediction modules and standalone FFNs are excluded.

Global-attention layers

10

Source: config · /layer_types | count full_attention

Layers whose KV cache grows with full context (dense or sparse global attention, MLA). Excludes sliding-window and linear/recurrent layers.

SWA : global

3

Calculated: attn.local_layers / attn.global_layers

attn.local_layers divided by attn.global_layers, the sliding-window to global interleave ratio (5 for '5 SWA : 1 global').

Sliding-window layers

30

Source: config · /layer_types | count sliding_attention

Layers with a fixed attention window.

Query heads

48

Source: config · /num_attention_heads

Global layers; SWA layers use 64 (attn.local_heads).

Query heads in the global-attention layers.

KV heads

8

Source: config · /num_key_value_heads

Key/value heads in the global-attention layers. Not applicable to MLA, whose cache is a shared latent.

Heads × head dim

6,144

Calculated: heads × head_dim

attn.heads × attn.head_dim, the query projection width of global layers.

Q heads / KV head

6

Calculated: heads / kv_heads

attn.heads divided by attn.kv_heads in global layers.

QK head dim

128

Source: config · /head_dim

Query/key dimension per head in global-attention layers (for MLA, nope + rope dims).

V head dim

128

Source: config · /head_dim

Value dimension per head in global layers (MLA v_head_dim; stated for MLA even when equal to the QK head dim).

Window

512 tokens

Source: config · /sliding_window

Sliding-window size of the local layers.

SWA KV heads

8

Source: config · /num_key_value_heads

LagunaAttention builds k_proj/v_proj from config.num_key_value_heads and config.head_dim for both layer types.

KV heads in sliding-window layers (stated even when equal to attn.kv_heads).

SWA query heads

64

Source: config · /num_attention_heads_per_layer/1

Layer 1 is sliding_attention; every sliding_attention entry is 64, every full_attention entry 48. modeling_laguna.py LagunaDecoderLayer.__init__ passes the per-layer count to LagunaAttention.

Query heads in sliding-window layers (stated even when equal to attn.heads).

SWA QK head dim

128

Source: paper · p.5 §3.1
In both types of layers, we use Grouped Query Attention (GQA) [3] with 8 KV heads, a head dimension of 128

Query/key head dimension in sliding-window layers. Value head dimensions may differ; see attn.local_v_head_dim.

Positional encoding

partial RoPE (global, first 50%), RoPE (SWA)

Source: paper · p.5 §3.1
GA layers use 48 Q-heads, θ = 500,000, and partial RoPE applied to the first 50% of the head dimension

Positional scheme in global layers: RoPE, partial RoPE, NoPE, or mixed per layer type.

RoPE base

500,000

Source: config · /rope_parameters/full_attention/rope_theta

Global layers; SWA layers use 10,000.

RoPE base frequency of the global layers at release.

SWA RoPE base

10,000

Source: config · /rope_parameters/sliding_attention/rope_theta

RoPE base frequency of the sliding-window layers (stated even when equal to attn.rope_theta).

Rotary fraction

0.5

Source: config · /rope_parameters/full_attention/partial_rotary_factor

Global layers; SWA layers rotate all dims (/rope_parameters/sliding_attention/partial_rotary_factor = 1.0).

Fraction of each head's QK dimensions that are rotated.

QK norm

Yes

Source: code · modeling_laguna.py; LagunaAttention.__init__
self.q_norm = LagunaRMSNorm(self.head_dim, eps=config.rms_norm_eps)

Queries and keys are normalized per head before the dot product.

Output gate

softplus, per head, on attention output before o_proj

Source: paper · p.5 §3.1
we use Grouped Query Attention (GQA) [3] with 8 KV heads, a head dimension of 128, and softplus-based per-head gating [67].

The model card says "sigmoid gating"; the report and released code (F.softplus on a per-head g_proj) use softplus. Config /gating (true) is not read by this modeling_laguna.py.

Gate applied to the attention output before the output projection, with its placement.

QKV bias

No

Source: config · /attention_bias

Query/key/value projections have bias terms.

Feed-forward

Activation

SwiGLU

Source: code · configuration_laguna.py; LagunaConfig defaults
hidden_act: str = "silu"

config.json sets no hidden_act; LagunaMLP computes down_proj(act_fn(gate_proj(x)) * up_proj(x)).

FFN activation (SwiGLU, GeGLU, ...).

Dense FFN dim

8,192

Source: config · /intermediate_size

Intermediate width of the dense FFN layers that are actually executed.

FFN bias

No

Source: code · modeling_laguna.py; LagunaMLP.__init__
self.gate_proj = nn.Linear(self.hidden_size, self.intermediate_size, bias=False)

FFN projections have bias terms.

Dense FFN / d_model

4

Calculated: ffn.dim / d_model

ffn.dim divided by shape.d_model.

Mixture of experts

Routed experts

256

Source: config · /num_experts

Routed experts per MoE layer.

Experts per token

8

Source: config · /num_experts_per_tok

Routed experts selected per token.

Shared experts

1

Source: paper · p.5 §3.1
plus a shared expert [20] that processes every token

Always-on experts per MoE layer.

Expert dim

512

Source: config · /moe_intermediate_size

Intermediate width of one routed expert.

Shared expert dim

512

Source: config · /shared_expert_intermediate_size

Total intermediate width of the shared expert(s).

Leading dense layers

1

Source: config · /mlp_layer_types | count dense

Number of initial blocks that use a dense FFN instead of MoE.

Router score

sigmoid

Source: paper · p.5 §3.1
We use a linear layer followed by a sigmoid activation as the routing function

Gating function over expert logits (softmax, sigmoid).

Load balancing

global-batch auxiliary loss (Qiu et al.) over non-padding tokens; padding tokens skip routing

Source: paper · p.5 §3.1
For load-balancing, we use an auxiliary loss from Qiu et al. [66] across the non-padding tokens of the global batch.

Coefficient not disclosed. Padding skip: §3.1.3.

Load-balancing method, with coefficients where disclosed.

Routed scaling factor

2.5

Source: paper · p.5 §3.1
The output of the routed experts is modulated by a coefficient of 2.5 before combining with the output of the shared expert.

Added in XS.2; M.1 has no routed-expert modulation (config /moe_routed_scaling_factor 2.5 here).

Multiplier applied to the combined routed-expert output (routed_scaling_factor).

Renormalize top-k

Yes

Source: paper · p.5 §3.1
apply normalization to the scores after top-k

Selected expert weights are renormalized to sum to 1.

Expert dim / d_model

0.25

Calculated: moe.expert_dim / d_model

moe.expert_dim divided by shape.d_model.

Sparsity (experts / top-k)

32

Calculated: experts / top_k

Routed experts divided by experts selected per token.

Active / total

0.0898204

Calculated: params.active / params.total

params.active divided by params.total.

Multi-token prediction

MTP depth

Not disclosed

Additional future tokens predicted during pretraining (0 when the model was trained without MTP).

Normalization and stability

Norm

RMSNorm

Source: paper · p.5 §3.1
with RMSNorm [103] as the normalization layer

Normalization layer type in the blocks.

Norm placement

pre

Source: paper · p.5 §3.1
using a pre-norm Transformer architecture

Pre-norm, post-norm, or sandwich (pre and post).

Norm epsilon

1e-06

Source: config · /rms_norm_eps

Epsilon of the block normalization layers.

Context length

Pretraining context

4.096K tokens

Source: paper · p.6 §3.1.1
The pre-training stage uses a context length of 4K tokens

Sequence length of the main pretraining stage.

Trained context

131.1K tokens

Source: paper · p.6 §3.1.1 Long-Context Training
the second extends the context to 128K tokens

Longest sequence length trained on after context extension.

Advertised context

262.1K tokens

Source: model-card · README.md; Model overview
Context window: 262,144 tokens

Longest context the publisher says the model supports, possibly beyond trained length via RoPE scaling.

Extension method

YaRN on global layers only; 4K → 32K → 128K (100B tokens each); 256K by doubling the global RoPE scale without training

Source: paper · p.6 §3.1.1 Long-Context Training
Both sub-stages apply YaRN [62] to global attention layers only

Released config /rope_parameters/full_attention: rope_type yarn, factor 64, original_max_position_embeddings 4,096, beta_fast 64, beta_slow 1, attention_factor 1.416; max_position_embeddings 262,144.

How context was extended (stages, RoPE base change, YaRN factor).

Pretraining recipe

Pretraining tokens

>30T

Source: paper · p.9 §3.2
In total, both models were trained on more than 30T tokens.

Tokens seen in pretraining including annealing and context extension, as reported.

Optimizer

Muon + AdamW (Moonlight variant; AdamW for non-matrix parameters)

Source: paper · p.6 §3.1.1
We use the Muon optimizer [39], specifically the Moonlight variant of Liu et al. [49], across all training stages

AdamW for non-matrix parameters with Moonlight-style LR scaling: §3.1.3.

Optimizer used for the bulk of parameters.

Peak LR

0.0005

Source: paper · p.6 §3.1.1
linear warmup to a peak learning rate of 5×10−4

WSD LR scaling law predicts ~5.5e-4; 5e-4 used for margin.

Peak learning rate of the main pretraining stage.

Final LR

2.5e-05

Source: paper · p.6 §3.1.1
ends at 5% of the peak (2.5×10−5 )

End of the main decay; long-context stages then decay to 5e-6.

Learning rate at the end of the decay.

LR schedule

WSD: linear warmup, stable at peak, 1−√ decay over the last 30% of steps to 5% of peak

Source: paper · p.6 §3.1.1
a final decay phase covering the last 30% of training steps that follows a 1−√⋅ shape and ends at 5% of the peak

Learning-rate schedule shape with phase boundaries.

Warmup

Not disclosed

Warmup length in steps or tokens.

Batch size

24M tokens

Source: paper · p.6 §3.1.1 Peak Learning Rate from a WSD Scaling Law
trains at B = 24M tokens

Long-context stages also use 24M tokens.

Global batch size, including any batch-size ramp: sequences × sequence length (token total), or the token total alone when only that is stated.

Batch (tokens)

24M tokens

Source: paper · p.6 §3.1.1 Peak Learning Rate from a WSD Scaling Law
trains at B = 24M tokens

Global batch size in tokens during the main pretraining stage, after any ramp (sequences × sequence length when stated in sequences, marked inferred).

Weight decay

Not disclosed

Decoupled weight decay coefficient.

Adam betas

Not disclosed

(beta1, beta2) of the Adam-family optimizer or its AdamW fallback.

Grad clip

Not disclosed

Global gradient-norm clipping threshold.

Training precision

BF16 mixed precision, FP32 master weights; selective FP32 in RMSNorm, RoPE and the LM-head input-gradient all-reduce

Source: paper · p.6 §3.1.1
We use BF16 mixed precision training throughout all stages with the master weights in FP32 and most computations in BF16

Matmul precision of pretraining (BF16, FP8 recipe, NVFP4 recipe) with the scaling granularity where disclosed. Never inferred from the released checkpoint dtype.

Stability measures

FP32 LM-head input-gradient all-reduce; no z-loss; padding tokens skip routing and load balancing

Source: paper · p.9 §3.1.3
We therefore enforce the LM head input-gradient all-reduce in FP32 while keeping the layer tensor-parallel, resolving this numerical instability.

Same section states "no z-loss" and the padding-token routing skip added for XS.2.

Interventions used during pretraining to keep it stable (QK-clip, z-loss, logit caps, spike handling), with coefficients.

Document masking

document masking; position ids reset at document boundaries

Source: paper · p.6 §3.1.2 Model Factory component: Titan
resetting position indices at document boundaries to avoid RoPE-related rounding under document masking in attention

Whether attention crosses document boundaries within a packed sequence.

Data mix

AutoMixer mix: raw code 30.6%, web 25.2%, synthetic/code-text 25.4%, math 9.0%, knowledge 6.6%, instruction-like 1.4%, academic papers 1.1%, books 0.7%; sampled from a ~27T unique-token pool

Source: paper · p.16 Table 4
Raw code 30.6% Web 25.2% Synthetic/code-text 25.4% Math 9.0% Knowledge 6.6% Instruction-like 1.4% Academic papers 1.1% Books 0.7%

Pool size: §3.2. Synthetic data is ~13% of the mix across all stages, from ~4.4T generated tokens (§3.2.2).

Pretraining data composition as disclosed (domain shares, synthetic fraction, repetition).

Hardware

2,048 H200

Source: paper · p.6 §3.1.1
LAGUNA M.1 and LAGUNA XS.2 were pre-trained on 6,144 and 2,048 NVIDIA H200 GPUs, respectively.

Accelerators used for pretraining, count and duration where stated.

Accelerators

2,048 H200

Source: paper · p.6 §3.1.1
LAGUNA M.1 and LAGUNA XS.2 were pre-trained on 6,144 and 2,048 NVIDIA H200 GPUs, respectively.

Accelerator count and type for the main pretraining run, as the count with thousands separators and the chip's short name ("2,048 H800", "2,048 GH200"). A stated range or bound stays as stated ("2,048–4,096 GH200").

Parallelism

EP8

Source: paper · p.7 §3.1.2
For MoE layers, we use Expert Parallelism, sharding expert weights across 8 H200 GPUs interconnected via NVLink.

Titan's mesh is (PP, DDP, FSDP, EGP, ETP) for MoE layers with ETP = 1 for M.1 and XS.2; other degrees not stated.

Parallelism layout of the main pretraining run as stated, as degree-annotated terms in the order TP, PP, VPP, EP, CP, DP ("PP16 · EP64 · ZeRO-1 DP"); a term without a stated degree has none ("FSDP").

Checkpoint averaging

EMA over the 10 most recent checkpoints at the end of the 128K stage

Source: paper · p.6 §3.1.1 Long-Context Training
we apply an exponential moving average (EMA) over the 10 most recent checkpoints from the end of the 128K stage and use the EMA weights as the final base checkpoint.

EMA or checkpoint merging applied to produce the released base weights.

Stages
  • main

    Seq len
    4096
    Lr
    0.0005
    Batch tokens
    24000000
    Source: paper · p.6 §3.1.1
    The pre-training stage uses a context length of 4K tokens

    WSD; tokens not disclosed

  • extend-32K

    Tokens
    100000000000
    Seq len
    32768
    Lr
    2.5e-05
    Batch tokens
    24000000
    Source: paper · p.6 §3.1.1
    split it into two equal-token sub-stages of 100B tokens each. The first sub-stage extends the context to 32K tokens

    cosine 2.5e-5 → 5e-6, no re-warmup; YaRN on global layers

  • extend-128K

    Tokens
    100000000000
    Seq len
    131072
    Lr
    2.5e-05
    Batch tokens
    24000000
    Source: paper · p.6 §3.1.1
    the second extends the context to 128K tokens

    cosine 2.5e-5 → 5e-6; EMA of the last 10 checkpoints is the final base

Source: paper · p.6 §3.1.1

Ordered pretraining stages. Each item: name, tokens, seq_len, lr, batch_tokens, batch_sequences, steps, note, quote, and source when it differs from the fact's source.

Scaling & HP transfer

HP selection rule

peak LR from WSD scaling law lr⋆(N, D) = 10^4.488 · N^−0.4639 · D^−0.2661 (N active params, D tokens incl. cooldown), scaled by √(B/B0) from B0 = 8M; predicts ~5.5e-4 at N = 3.0B, B = 24M; 5e-4 used

Source: paper · p.6 §3.1.1 Peak Learning Rate from a WSD Scaling Law, Eq. 1
To pick the peak LR for LAGUNA XS.2 at production scale, we therefore fit a WSD-specific scaling law

How peak LR, batch size or other hyperparameters were chosen for the released run (fitted scaling law with its formula, μP transfer from a proxy width, sweep), as stated.

Scaling ladder

LR-law sweep: 4 MoE sizes (2B–16B total / 0.3B–2.2B active) × 6 LRs × 5 token budgets (30B–480B) at 8M batch; architecture ablations on a 16.6B-total / 2.3B-active proxy (22 layers, d_model 2048, 128 experts top-8, 335B tokens); data mixture from ~60 × ~0.5B MoE proxies on ~60B tokens

Source: paper · p.6 §3.1.1; App. A.1–A.2, Table 8; §3.2.3 AutoMixer
sweeping four MoE sizes (2B–16B total / 0.3B–2.2B active) across six learning rates and five token budgets

Appendix A.1 instead lists D ∈ {60, 120, 240, 480, 960}B and B0 = 8.4M tokens.

Smaller models trained to choose the architecture or recipe (sizes, token budgets), as disclosed.

KV cache

KV bytes / token

41,440 bytes

Calculated: kv.bytes_at_context / 131072 tokens; uniform BF16, payload only; quantization overhead excluded. Global KV: 10 × (2048 × 16/8) B/entry; SWA KV: 30 × (2048 × 16/8) B/entry

Retained KV cache divided by context length, including bounded SWA caches and indexer keys. Exports use uniform BF16 at 131,072 tokens. The website can select uniform payload precision (no quantization overhead) or sourced component formats (including scales and documented padding). This is cache payload, not peak prefill memory or persistent prefix storage.

Global KV bytes / token

40,960 bytes

Calculated: 40960 B / 1 tokens (Global KV); uniform BF16, payload only; quantization overhead excluded. Global KV: 10 × (2048 × 16/8) B/entry; SWA KV: 30 × (2048 × 16/8) B/entry

Long-context global KV bytes per token, including indexer keys; excludes bounded SWA caches. Compression rates and cross-layer cache reuse are included. Exports use uniform BF16; the website's storage selector also applies here. This is the field to compare with global-KV figures in reports, using the matching storage recipe.

KV bytes / token / B active

13,813 bytes

Calculated: kv.bytes_per_token (131072 tokens) / (params.active / 1e9); uniform BF16, payload only; quantization overhead excluded. Global KV: 10 × (2048 × 16/8) B/entry; SWA KV: 30 × (2048 × 16/8) B/entry

kv.bytes_per_token divided by active parameters in billions (131,072 tokens in exports).

KV at context / B active

1,810,541,227 bytes

Calculated: kv.bytes_at_context (131072 tokens) / (params.active / 1e9); uniform BF16, payload only; quantization overhead excluded. Global KV: 10 × (2048 × 16/8) B/entry; SWA KV: 30 × (2048 × 16/8) B/entry

kv.bytes_at_context divided by active parameters in billions (131,072 tokens in exports).

KV at context

5,431,623,680 bytes

Calculated: 40960 B × 131072 (Global KV) + 122880 B × min(131072, 512) (SWA KV); uniform BF16, payload only; quantization overhead excluded. Global KV: 10 × (2048 × 16/8) B/entry; SWA KV: 30 × (2048 × 16/8) B/entry

Retained KV cache for one sequence at the selected context, including SWA windows and indexer keys. Exports use uniform BF16 at 131,072 tokens. Excludes recurrent state, compressor tail state, draft/MTP caches, temporary prefill tensors, allocator metadata and persistent prefix snapshots. Does not estimate peak prefill or total serving memory.

All models · Link to this model