Post
887
š Adding a GPU without building one
AI is usually framed as "how smart is the model / how many GPUs did you buy." The real bottleneck is elsewhere ā how efficiently you use the GPUs you already have.
Training happens once; inference runs the entire time users use your product. So a service's economics come down to cost per token. Inference acceleration uses software to pull several times more out of the same GPU ā the effect of plugging in one more "virtual GPU."
VIDRAFT's VKAE, measured (B200, same-harness, no quality loss):
Qwen3.5-35B-A3B (MoE): 25.7 ā 601 tok/s (23.4Ć)
Darwin-36B-Opus (in-house MoE): 25.0 ā 280.8 (11.2Ć)
10,000+ tok/s peak aggregate under concurrency
The key: it's reproducible ā model + serving shipped as one container.
docker pull vidraft/qwen35-vkae:601
Don't take our word for it ā run it yourself. The mechanism will be released as a paper.
š Leaderboard & demo š VIDraft/vkae
Articles š https://huggingface.co/blog/FINAL-Bench/vkae-leaderboard
AI is usually framed as "how smart is the model / how many GPUs did you buy." The real bottleneck is elsewhere ā how efficiently you use the GPUs you already have.
Training happens once; inference runs the entire time users use your product. So a service's economics come down to cost per token. Inference acceleration uses software to pull several times more out of the same GPU ā the effect of plugging in one more "virtual GPU."
VIDRAFT's VKAE, measured (B200, same-harness, no quality loss):
Qwen3.5-35B-A3B (MoE): 25.7 ā 601 tok/s (23.4Ć)
Darwin-36B-Opus (in-house MoE): 25.0 ā 280.8 (11.2Ć)
10,000+ tok/s peak aggregate under concurrency
The key: it's reproducible ā model + serving shipped as one container.
docker pull vidraft/qwen35-vkae:601
Don't take our word for it ā run it yourself. The mechanism will be released as a paper.
š Leaderboard & demo š VIDraft/vkae
Articles š https://huggingface.co/blog/FINAL-Bench/vkae-leaderboard
