jdopensource · video

JoyAI-Echo

jdopensource/JoyAI-Echo

JoyAI-Echo at Q4_K_M is exactly 15,694,613,568 bytes (14.62 GiB / 15.69 GB) — an effective 10.298 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
12.2B
Architecture
joyai-gemma
null layers
Context
native (config.json)
License

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K8.54 GiB9,165,048,8966.014realrebelai
Q5_19.23 GiB9,915,282,4966.506realrebelai
Q8_012.45 GiB13,366,760,8968.771realrebelai
Q4_K_M14.62 GiB15,694,613,56810.298realrebelai
Q6_K18.23 GiB19,573,124,16012.843realrebelai

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
denoiser42.97 GiB100%no, must be resident
Full pipeline42.97 GiBresident if nothing is offloaded

The parameter count published for a diffusion model describes the denoiser alone. Running it also requires its text encoder and VAE, and the text encoder is often nearly as large as the denoiser — which is why offloading it is the standard first move when you run out of memory.

We publish component sizes here, not throughput. Community-submitted image-generation rates do exist for many GPUs and we show them on the hardware pages, but they aggregate runs at different resolutions, step counts and settings, so they cannot be attributed to one model. Peak memory during sampling is unmeasured by any public source, and we do not estimate it.

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 6.39 GiB. The real file is 14.62 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
Attention heads
KV heads
Head dim
Hidden size
Vocab
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does JoyAI-Echo need?
Q4_K_M is exactly 15,694,613,568 bytes (14.62 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of JoyAI-Echo 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.