kai-os · text

Carnice-V2-27b

kai-os/Carnice-V2-27b

Carnice-V2-27b at Q4_K_M is exactly 16,547,399,264 bytes (15.41 GiB / 16.55 GB) — an effective 4.839 bits per weight, not the nominal 4. Its KV cache at 32K is 2.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
27.4B
Architecture
qwen35
64 layers
Context
262,144
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
I1-IQ1_S6.66 GiB7,149,824,2242.091mradermacher
I1-IQ1_M7.11 GiB7,631,083,7442.232mradermacher
I1-IQ2_XXS7.85 GiB8,433,182,9442.466mradermacher
I1-IQ2_XS8.47 GiB9,090,590,9442.658mradermacher
IQ2_XXS8.53 GiB9,154,058,0482.677bartowski
I1-IQ2_S8.72 GiB9,362,913,5042.738mradermacher
IQ2_XS9.08 GiB9,747,814,2082.851bartowski
IQ2_M9.32 GiB10,004,592,4482.926kai-os
I1-IQ2_M9.32 GiB10,004,592,8642.926mradermacher
IQ2_S9.37 GiB10,056,345,4082.941bartowski
I1-Q2_K_S9.54 GiB10,248,325,3442.997mradermacher
IQ2_M9.90 GiB10,634,372,9283.110bartowski
Q2_K9.98 GiB10,711,664,2243.132kai-os
I1-Q2_K9.98 GiB10,711,664,8643.132mradermacher
I1-IQ3_XXS10.42 GiB11,186,370,7843.271mradermacher
Q2_K10.80 GiB11,600,455,4883.392bartowski
I1-IQ3_XS11.15 GiB11,967,129,8243.500mradermacher
I1-Q3_K_S11.24 GiB12,073,953,5043.531mradermacher
IQ3_XXS11.54 GiB12,387,788,6083.623bartowski
I1-IQ3_S11.57 GiB12,419,328,2243.632mradermacher
I1-IQ3_M11.72 GiB12,580,874,4643.679mradermacher
Q2_K_L11.96 GiB12,842,055,4883.755bartowski
IQ3_XS12.19 GiB13,091,419,9683.828bartowski
I1-Q3_K_M12.39 GiB13,301,442,7843.890mradermacher
Q3_K_S12.56 GiB13,481,359,1683.942bartowski
IQ3_M12.73 GiB13,664,532,2883.996bartowski
I1-Q3_K_L13.36 GiB14,344,775,9044.195mradermacher
Q3_K_M13.38 GiB14,366,750,5284.201bartowski
Q3_K_L14.01 GiB15,040,460,6084.398bartowski
I1-IQ4_XS14.05 GiB15,082,506,4644.411mradermacher
IQ4_XS14.28 GiB15,328,839,4884.483bartowski
I1-Q4_014.46 GiB15,521,433,8244.539mradermacher
I1-Q4_K_S14.52 GiB15,586,314,4644.558mradermacher
IQ4_NL14.98 GiB16,086,845,2484.704bartowski
Q4_015.00 GiB16,109,782,8484.711bartowski
Q4_K_S15.34 GiB16,474,163,0084.818bartowski
Q4_K_M15.41 GiB16,547,399,2644.839kai-os
I1-Q4_K_M15.41 GiB16,547,399,9044.839mradermacher
I1-Q4_115.91 GiB17,078,241,5044.994mradermacher
Q4_K_M16.33 GiB17,533,552,4485.127bartowski

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.25 GiB1.00 GiB4.00×16 / 0 / 48
8,1920.50 GiB2.00 GiB4.00×16 / 0 / 48
16,3841.00 GiB4.00 GiB4.00×16 / 0 / 48
32,7682.00 GiB8.00 GiB4.00×16 / 0 / 48
65,5364.00 GiB16.00 GiB4.00×16 / 0 / 48
131,0728.00 GiB32.00 GiB4.00×16 / 0 / 48

48 of 64 layers use linear attention, which keeps a fixed-size recurrent state instead of a per-token cache. Those layers do not grow with context at all — treating them as ordinary attention, as a flat formula does, overstates this model's cache by roughly 4.0× at long context.

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 14.33 GiB. The real file is 15.41 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
64
Attention heads
24
KV heads
4
Head dim
256
Hidden size
5120
Vocab
248,320
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does Carnice-V2-27b need?
Q4_K_M is exactly 16,547,399,264 bytes (15.41 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Carnice-V2-27b's KV cache?
2.00 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of Carnice-V2-27b should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.