neko-legends/dual-spark-optimizations — explained in plain English
Analysis updated 2026-05-18
Configure two connected DGX Spark machines to serve a large language model with automatic single- and multi-request handling.
Compare measured throughput across different serving profiles before choosing a configuration for a two-node GPU cluster.
Set up a direct high-speed network link between two GPU nodes for model serving and inference.
Reference real benchmark numbers when evaluating tradeoffs between single-request speed and concurrent throughput.
| neko-legends/dual-spark-optimizations | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | Python | Python | Python |
| Last pushed | — | 2022-11-22 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 5/5 | 2/5 | 4/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires two physical DGX Spark machines with a direct high-speed network link and approved access to gated model weights.
dual-spark-optimizations is a configuration project for running a large language model quickly across two NVIDIA DGX Spark machines connected directly to each other. It combines two existing open source projects, a set of modified model weights and a fast two-node serving runtime built on vLLM, into one tested setup, rather than introducing new model code of its own. The main contribution is a serving option called the adaptive profile, which the README recommends as the default for most users. It automatically behaves like a fast single-request setup when only one request is active, and switches to handling up to four requests at once when traffic overlaps, without needing any special flag or model reload. Two other profiles are also included: a fast profile tuned purely for single-request speed, and a long-c4 profile that supports a much larger one-million-token context window at the cost of some speed. The README backs its claims with detailed benchmark tables measured on an actual two-Spark cluster, comparing decode speed and aggregate throughput across different prompt sizes and profiles, along with network fabric test results showing the direct high-speed connection between the two machines. It is upfront that these numbers are specific to this hardware and model combination and not directly comparable to results from other setups. Setting it up requires two DGX Spark machines connected by a single cable, Ubuntu 24.04, Docker and Docker Compose, matching Linux usernames on both machines, and approved access to the gated model weights on Hugging Face, since the model itself is not included in the repository. The README walks through cloning the repo, filling in a configuration file with machine specific values, and a script that checks and fixes duplicate machine IDs that can occur on cloned factory images before the two nodes are connected. This is a specialized project aimed at people who already own or have access to this specific two-node hardware setup.
A configuration project that tunes a fast, two-node serving setup for running a large language model across two connected NVIDIA DGX Spark machines.
Mainly Python. The stack also includes Python, vLLM, Docker.
No license information was found in the README, the underlying model weights carry their own separate usage agreement.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.