antirez's DwarfStar (ds4): A Deliberately Narrow Local LLM Inference Engine
What does the creator of Redis build next? Salvatore Sanfilippo's (antirez's) answer is DwarfStar (ds4)—a deliberately narrow local inference engine. Currently trending on GitHub at +385 stars/day, it looks modest, but it represents the Redis author's new direction twenty years later.
Continuation of the Redis Philosophy
Redis succeeded by "doing one thing extremely well"—not building a database that does everything, but building the fastest in-memory cache. Two decades later, antirez applies the same philosophy to inference engines:
> DwarfStar is self-contained and deliberately narrow, not a general GGUF runner.
Rather than a general GGUF runner, ds4 supports only three models: DeepSeek V4 Flash, GLM 5.2, and DeepSeek V4 PRO—but pushes each to its limits.
Why Not vLLM or llama.cpp?
The local inference engine space is crowded. antirez's response: general GGUF runners make too many compromises to support every model. vLLM no longer supports older GPU architectures (e.g., Ada Lovelace), rendering many L40S cards obsolete in enterprise fleets.
ds4's opportunistic strategy: follow the best open-weight releases, run only these models, but run them the fastest and best. Models can be swapped as better open weights emerge.
Technical Highlights
Backends
- Metal: Primary target for Macs with 96GB+; smaller machines use SSD streaming
- NVIDIA CUDA: Including multi-GPU systems and DGX Spark
- ROCm: Strix Halo systems (e.g., Framework Desktop)
- 120 t/s aggregate generation throughput
- 2000 t/s prefill
- SSD streaming: Stream model weights from SSD when RAM is insufficient; runs on MacBook
- Tensor parallelism: Two MacBook M5 Max / M3 Ultra units via RDMA running 4-bit DeepSeek Flash or GLM 5.2
- Pipeline parallelism: Chain multiple systems to combine RAM for larger models
- Micro-batching: Separate decoding and generation batches
- colibrì (1300 lines of C running a 744B-parameter model): small, precise C code still has a place in AI infrastructure
- Euclid-MCP (outsourced reasoning): specialized tools for specialized tasks rather than one general system
- vLLM dropping older cards: a general system's compromise is a specialized system's opportunity
- General GGUF runner = Swiss Army knife: does everything, masters nothing
- ds4 = Surgical scalpel: cuts one way, cuts perfectly
- Redis then = fastest in-memory cache, no OLTP ambitions
- ds4 now = fastest DeepSeek Flash runner, no other-model ambitions
- Repository: https://github.com/antirez/ds4
- Author: Salvatore Sanfilippo (antirez, creator of Redis)
- License: MIT
- Backends: Metal / CUDA / ROCm
Measured Performance
Multi-user session tests on 8xL40S NVIDIA cards:
This turns "cards vLLM abandoned" into viable multi-user LLM servers—likely the most practical selling point for enterprises with legacy GPUs.
Other Features
Self-Contained
Model loading, prompt rendering, tool calls, KV state, HTTP server, coding agent—all built and tested together. Not assembled from components; a fully integrated engineering effort.
Transparent AI-Assisted Development
The ds4 README contains a rare candid disclosure:
> This software is developed with strong assistance from GPT 5.5, 5.6, Claude Fable and with humans leading the ideas, testing, and debugging. We say this openly because it shaped how the project was built. If you are not happy with AI-developed code, this software is not for you.
antirez doesn't hide AI assistance—he openly acknowledges it shaped the project. Humans lead ideas, testing, and debugging; AI leads code generation. This is a new engineering paradigm: human architect + AI programmer.
Acknowledging llama.cpp
ds4 does not link GGML, but the README states clearly:
> This project would not exist without llama.cpp and GGML.
Certain source-level fragments (GGUF quantization layout, CPU quant/dot logic, specific kernels) are retained or adapted under MIT. antirez even preserves the GGML author's copyright notice in the LICENSE file. This represents an ideal open-source interaction—standing on predecessors' shoulders, openly crediting them, preserving attribution. Not a fork, but a tribute-style independent implementation.
Engineering Insight: The Victory of Deliberate Narrowness
ds4's design philosophy resonates with recent work:
These projects point to one theme: within the "bigger and stronger" AI narrative, "deliberately narrow" is an underrated strategy.
Analogies
Conceptual Lineage: Division of Labor Beats Unification
ds4 belongs to the "division of labor beats unification" lineage—not pursuing one inference engine for all models, but letting specialized engines handle specialized models. The same family of thought as octopus DNA pretraining + RNA inference, Euclid-MCP's LLM + Prolog division, and Rebucca's small-model + large-model verification.
Conclusion
antirez took the opposite path of the mainstream. In the inference engine arms race of "support more models, more parameters," ds4 answers: "support fewer models, run faster." Redis proved "deliberate narrowness" wins in databases—ds4 tests whether it holds in inference engines.
If successful, it offers more than another inference engine—it provides a counterintuitive template for AI infrastructure: in an era of generalization, deliberate narrowness may be an underrated competitive advantage.
---