What GPU do I need to run yuxinlu1/gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2?

12.0B parameters, published in F16. View on Hugging Face

12.0B
Parameters
F16
Native precision
Gemma4UnifiedForConditionalGeneration
Architecture
text-generation
Pipeline

gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2 is published by yuxinlu1 on Hugging Face, with 71,786 downloads and 97 likes to date. It's a Gemma4UnifiedForConditionalGeneration model built for text-generation, published natively in F16.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
FP1622.3 GB26.7 GBV1001$0.220/hr
FP8 (quantized)11.1 GB13.4 GBRTX 5060 Ti1$0.145/hr
INT4 (quantized)5.6 GB6.7 GBRTX 30701$0.088/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2 at its published (F16) precision: 1× V100, at $0.220/hr per GPU ($0.220/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Sliding-window attention: windowed layers stop growing at the window, the full-attention layers keep growing. Cached per token: 393,216 bytes at 16-bit while the context is inside the window.

ContextKV cache, one sequence
4K0.56 GB
32K2.3 GB
128K8.3 GB
256K (model maximum)16.3 GB

Computed from the layer, head and window counts in the model's own configuration (yuxinlu1/gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2: common questions

Does gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2 fit on a 32 GB GPU?

Yes. At FP16 it needs 26.7 GB of VRAM, so a 32 GB card holds it with 5.3 GB to spare. A 24 GB card is not enough for it at FP16.

What is the least VRAM gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2 can run in?

6.7 GB, at INT4 (quantized), which fits an 8 GB card, against 26.7 GB at FP16. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2 lower the GPU bill?

Yes. At FP16 the cheapest live fit is one V100 at $0.220/hr. At INT4 (quantized) it drops to one RTX 3070 at $0.088/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Gemma 4 models

All 44 Gemma 4 models: VRAM and GPU requirements

Lineage

Based on gemma-4-12B-it.

Alternatives at this size

Other models for text-generation within about a third of gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2's 12.0B parameters, from other model lines.

More on gemma-4-12B-agentic-fable5-composer2.5-v2-3.5x-tau2

Related reading: V100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, Best GPU for LLM inference, and What AI model fine-tuning is.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.