Skip to content
Skip to documentation content
Browse documentation

Lab builds

A model matrix tells you what runs. A lab build tells you what it took.

Each page here is one configuration that was actually stood up and measured: the machines and their fabric, the model artifact and where it came from, the InferenceService as deployed, the throughput and memory numbers that came out of it, and the failures that cost time on the way. They are reference points, not recommendations. Your hardware will differ and so will your numbers.

These pages exist because the gap between “this model fits” and “this model serves” is mostly undocumented. Quantisation choices, KV cache dtype, chunk sizes, speculative decoding, RDMA GID indexes and image tags all move throughput by more than the model choice does, and almost none of it is written down anywhere you can copy.

Builds

BuildHardwareModelShape
DeepSeek V4 Flash Vision on two DGX Sparks2x GB10, 200 Gb RoCEDeepSeek-V4-Flash-Vision-ExpvLLM, TP2 + expert parallel, speculative decoding
GLM-5.3-Flash EXL3 on two DGX Sparks2x GB10, CX7 RoCEGLM-5.3-Flash EXL3/TR3 4bpwvLLM, TP2, DFlash2 speculative decoding, self-built runtime
Qwen3.8-Flash-Next with MTP on one Strix Halo1x Ryzen AI Max+ 395, gfx1151Qwen3.8-Flash-Next UD-Q3_K_XLllama.cpp Vulkan, MTP speculative decoding, upstream pin plus one vendored PR

What a build page contains

  1. Why this combination, and what it is for.
  2. Hardware, including the fabric and how the nodes are cabled.
  3. The model artifact: format, size on disk, and how it is staged.
  4. The manifests, complete enough to apply.
  5. Measured results, with the client path and prompt shape stated, because both change the numbers.
  6. What went wrong, which is usually the most reusable part.

Contributing a build

Lab builds are welcome, including ones on hardware nobody else has. The bar is that the numbers came from a run you did, the manifests are the ones you applied, and the failures are recorded honestly. State the image tags and the commit or build string of the runtime; a throughput figure without them is not reproducible. Open a pull request adding a page here and a row in the table above.

LLMKube LLMKube

Kubernetes for Local LLMs. Deploy, manage, and scale AI inference workloads with production-grade orchestration.

© 2026 Defilan Technologies LLC

Community

Built for the Kubernetes and AI communities

LLMKube is not affiliated with or endorsed by the Cloud Native Computing Foundation or the Kubernetes project. Kubernetes® is a registered trademark of The Linux Foundation.