Two Sparks Run DeepSeek-1017 With the Drafter on Two RTX 3090s
An x86 server holds the Engram tables and the drafter; 49.7 to 66.2 tok/s per request.
Move the drafter and the Engram tables off the Sparks, and the freed memory goes to context.
@NicoTheGreco posted a progress report from PLI Labs on a fully local DeepSeek-V4.1-Flash-1017. The target model, an EXL3 build at about 2.75 bits per weight, runs across two DGX Sparks over their direct 200 Gb RoCE link.
Two parts move to an ordinary x86 server with 512 GB of RAM and four RTX 3090s. The DSpark drafter, which proposes up to five tokens per round, runs on two NVLinked 3090s. DeepSeek’s Engram tables, about 189 GiB, sit in the server’s RAM, and each Spark reads rows over its own 40 Gb/s RDMA link. The Sparks still verify every token, so the output keeps the target model’s distribution.
| Prompt | First token | Decode tok/s |
|---|---|---|
| 124 tokens | 0.36 s | 49.7–53.1 |
| 32,000 tokens | 14.5 s | 58.7–66.2 |
| 150,000 tokens | 68.6–68.7 s | 53.0–54.9 |
Prompt reading runs about 2,200 tokens a second up to 150K. Three 32K requests at once made about 105 tok/s combined. The production limit is 327,680 tokens per request; a 524,288-token profile works but is held back for a prefill slowdown, and 1M was not tested.
Sources
- @NicoTheGreco on X · Oct 23, 4:28 PM PT
- PLI Labs progress report · github.com