Qwen-Image-2.1 vs sd-turbo

Qwen-Image-2.1 (7.1B parameters) and sd-turbo (866M parameters) side by side: the memory each needs at every precision, what it costs to run on a live GPU, and the context window, KV cache and license where they are published. Numbers are computed from the models' published specs; this page does not rank quality.

Side by side

FactQwen-Image-2.1sd-turbo
Parameters7.1B866M
Architecture––
License––
Published precisionBF16F32
VRAM needed, As published15.9 GB3.9 GB
VRAM needed, FP88.0 GB1.0 GB
VRAM needed, INT44.0 GB0.5 GB
Cheapest live fit, As publishedRTX A4000 · $0.167/hrRTX 3070 · $0.088/hr
Cheapest live fit, FP8RTX 4070 · $0.154/hrRTX 4070 · $0.154/hr
Cheapest live fit, INT4RTX 3070 · $0.088/hrRTX 3070 · $0.088/hr

VRAM is the weight size at each precision times a flat 1.2 overhead; see the methodology. The FP8 and INT4 rows need a quantized checkpoint or an engine that quantizes on load. The fit is the lowest-priced single GPU type that holds the model at that precision, or the lowest-priced multi-GPU set (up to 8) when none does.

Which to pick

  • sd-turbo needs less VRAM at its published precision (3.9 GB against 15.9 GB), so it fits on a smaller GPU.
  • sd-turbo has the cheaper live GPU fit at its published precision ($0.088/hr against $0.167/hr).

These follow only from the facts in the table above. Whether either model does your task well is a separate question this page does not answer.

Keep reading

Other comparisons

Start ComfyUI on a rented GPU.

© 2026 Aquanode. All rights reserved.

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