What is this, and why does it seem confusing?
Select a model card to add its recipe to the comic panel. The panel's layout and artwork change based on the selected model and the number of DGX Sparks in your cluster.
If you prefer to skip the visual interface, go directly to the GB10SOR GitHub repository and find the exact nix develop command for the model you want to run.
New here? Start with Quickstart. Tap a question for the short answer.
Why change from DGX OS to NixOS?
To save your setup as files: drivers, packages, services, and settings. That makes another Spark easier to configure and a bad software update easier to roll back. It takes more setup than the factory OS and does not automatically make models faster. How NixOS works.
Why install alongside DGX OS?
Keep a familiar fallback and NVIDIA’s update tools for firmware such as UEFI and the embedded controller. Boot into DGX OS when you need them. NVIDIA’s update guide.
NixOS can also receive supported firmware updates through Graham’s module. Keeping DGX OS gives you another recovery path. The GB10SOR AArch64 installer was verified to detect the internal NVMe and offer installation alongside DGX OS. Use only its matching published checksum and stop if the installer cannot clearly preserve DGX OS, recovery, and EFI. Firmware support.
Why run NixOS headless?
Headless means no desktop running on the Spark. After setup, manage it from your laptop using SSH, a remote terminal. There are fewer desktop apps to maintain and more memory left for workloads. It is optional: NixOS can run a desktop, too. Keep a keyboard and monitor handy for recovery.
Why do reproducible builds matter?
They make “works on my Spark” easier to repeat. Pin software versions and save the configuration so someone else can rebuild the same environment. Also record the model files, engine, and settings. This helps debugging and fair comparisons; it does not guarantee identical answers or speed. How Nix works.
Can I use both QSFP56 ports at once?
Yes. Both rear ConnectX-7 QSFP ports can be connected. Use compatible cables and your recipe’s port layout; plug shape alone does not prove compatibility. Insert with the pull-tab up, without force. The network still needs configuration. NVIDIA’s cable guide.
A second cable does not guarantee twice the speed. Graham’s two-Spark setup reaches its target with one cable; both ports share the host connection. Other layouts may use both to reach different Sparks. Graham’s networking notes.
What benchmarks should I expect for each lane?
There is no honest tokens-per-second number based on Spark count alone. Earlier GB10SOR results were local tests, not a performance promise.
| Lane | Sparks | What to compare |
|---|---|---|
| Solo | 1 | Your baseline: one model on one Spark. |
| Deuces | 2 | The same workload over direct or switch links. |
| Trips | 3 | Model fit and the cost of moving data between nodes. |
| Quads | 4 | Single-request speed and several requests at once. |
| Eights | 8 | Larger-model capacity and scaling across all eight. |
These are test goals, not measured speeds. More Sparks may fit larger models or serve more users; one reply can still be slower. Compare the same model, quantization, engine, context, and request count. Measure time to first token, prompt processing, and generation speed.
One upstream reference: Graham reports 23.2 GB/s in a two-Spark, 16 GB NCCL all-gather test. That measures communication, not model tokens/s. Read the test.
Why NixOS rather than Guix?
Guix also supports reproducible environments and rollbacks. We use NixOS because Graham’s Spark support and our recipes already use Nix. Guix’s official system uses Linux-libre and free firmware; NVIDIA’s proprietary CUDA stack would need separate integration. We have not validated a Guix path. Guix’s hardware policy.
Can I try Nix without replacing DGX OS?
Yes. Nix is a package manager; NixOS is an operating system. Graham lists which playbooks work on DGX OS. The GB10SOR quickstart covers the repository workflow on DGX OS or NixOS. Graham’s compatibility table. GB10SOR quickstart.
Will one nix develop command set up everything?
No. One-command launch comes after setup. Current cluster recipes expect configured NixOS hosts, matching drivers, downloaded model files, SSH access, and the right cabling and network settings. Some check exact host names and system builds. A different network can fail until the configuration is adapted. Start here.
