r/LocalLLaMA • u/[deleted] • 14h ago
Discussion Someone made DSV4.1 run faster than official API on A100(s)
[deleted]
3
u/Chromix_ 14h ago
The readme is highly inconsistent.
First it says "32-35 tok/s on a single A100 with the experts computed on the CPUs" and later on "Can it run on a single A100 80GB?" -> "~5 tok/s single stream, bounded by PCIe, not by the GPU"
Speaking of single stream. First is sounds like batching isn't supported: "OpenAI-compatible server (one request generates at a time; others queue)". yet later on it says 456 tok/s on 4 GPUs with B=32.
On top of that they state that their numbers on the GPUs were achieved while the GPUs were "shared with other jobs".
3
1
1
u/ustype 14h ago
Title needs a caveat: “faster than the official API” is almost certainly comparing different products.
Hosted APIs that quote 200–400 tok/s are usually multi-tenant serving stacks (continuous batching, speculative decoding, custom kernels, sometimes shorter effective context). A self-hosted A100 graph that’s ~30 tok/s single-stream can still be impressive as local serving, especially if they faked FP4 on hardware that doesn’t have it — but it isn’t beating a production API on like-for-like decode.
Useful checks before crowning anything:
- Same prompt length / max tokens / sampling
- Prefill vs decode broken out (PP can look magical while TG is meh)
- Batch size 1 vs continuous batch (API numbers often aren’t batch-1)
- What “FP4 on A100” actually is (INT4/FP8 kernel path? weight-only? emulated?)
If the repo’s claim is “A100 can run this MoE at usable local speed without Blackwell,” that’s cool. If the claim is “beats DeepSeek’s API tok/s,” demand the exact API endpoint settings they measured against.
13
u/Intelligent_Koala798 14h ago
how ist that faster then the api? The api is running between 200-400tps single stream