Z-Image-Turbo โ€” fni8 (int8/W4A8 dp4a, Volta sm_70)

Diffusion transformer (DiT), quantized from Tongyi-MAI/Z-Image-Turbo. Repackaged to the .fni8 resident format (~6.3 GB) for the fni8 W8A8/W4A8 DP4A kernels on NVIDIA Volta (sm_70) โ€” Tesla V100 / CMP 100-210.

Status

Validated: end-to-end ComfyUI-fni8 sanity pass. Measured int8-vs-fp quality on this DiT: PSNR ~29โ€“31 dB, SSIM ~0.95. Performance is fleet-specific. All fni8 speedups are measured on the CMP 100-210 mining-card fleet, where the fp16 tensor cores are firmware-gimped. These numbers do not transfer to a real Tesla V100 (whose fp16 tensor cores would beat dp4a).

Format

  • Weights: int4 per-group W4A8 (int8 activations), fp32 scales, resident dp4a VRAM layout.
  • Why dp4a: sm_70 has no int8 tensor cores, so the matmul contraction runs on the __dp4a CUDA-core intrinsic. On the CMP 100-210 fleet (whose fp16 tensor cores are firmware-limited) dp4a is the fast path, not a compromise.

How to run

ComfyUI-fni8 is the runtime (UnetLoaderFNI8 runs the diffusion transformer through the dp4a kernels; the text encoder and VAE are unchanged). fni8-serve is for LLMs only and does not load this model.

Limitations

  • Quantization is lossy: int8 (and especially int4) outputs differ from the fp16/bf16 parent, and the difference varies by task.
  • Capabilities, biases, and risks of the parent model carry over โ€” see the parent card.
  • This is a derivative quantization, not a relicense; the parent model's license and acceptable uses apply.

Part of the fni8 stack: kernels ยท LLM serving ยท ComfyUI DiTs.

Downloads last month

-

Downloads are not tracked for this model. How to track
Inference Providers NEW
This model isn't deployed by any Inference Provider. ๐Ÿ™‹ Ask for provider support

Model tree for jajmangold/Z-Image-Turbo-fni8

Quantized
(70)
this model