whatisgithub

What is dual-spark-optimizations?

neko-legends/dual-spark-optimizations — explained in plain English

Analysis updated 2026-05-18

0PythonAudience · ops devopsComplexity · 5/5Setup · hard

In one sentence

A configuration project that tunes a fast, two-node serving setup for running a large language model across two connected NVIDIA DGX Spark machines.

Mindmap

mindmap
  root((dual-spark-optimizations))
    What it does
      Two node LLM serving
      Adaptive request scaling
      Benchmark reporting
    Tech stack
      vLLM
      Docker
      DGX Spark
    Use cases
      Multi node inference setup
      Throughput benchmarking
      Fabric configuration
    Audience
      DevOps engineers
      ML infra owners
    Setup
      Two connected DGX Sparks
      Gated model access

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Configure two connected DGX Spark machines to serve a large language model with automatic single- and multi-request handling.

USE CASE 2

Compare measured throughput across different serving profiles before choosing a configuration for a two-node GPU cluster.

USE CASE 3

Set up a direct high-speed network link between two GPU nodes for model serving and inference.

USE CASE 4

Reference real benchmark numbers when evaluating tradeoffs between single-request speed and concurrent throughput.

What is it built with?

PythonvLLMDockerDocker ComposeUbuntu

How does it compare?

neko-legends/dual-spark-optimizations0xallam/my-recipe0xhassaan/nn-from-scratch
Stars00
LanguagePythonPythonPython
Last pushed2022-11-22
MaintenanceDormant
Setup difficultyhardmoderatemoderate
Complexity5/52/54/5
Audienceops devopsgeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Requires two physical DGX Spark machines with a direct high-speed network link and approved access to gated model weights.

No license information was found in the README, the underlying model weights carry their own separate usage agreement.

So what is it?

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.

Copy-paste prompts

Prompt 1
Walk me through setting up the .env file and network fabric for dual-spark-optimizations on two DGX Spark machines.
Prompt 2
Explain the difference between the adaptive, fast, and long-c4 serving profiles in this project.
Prompt 3
Help me interpret the benchmark tables in this repo comparing C1 and C4 throughput across profiles.
Prompt 4
Explain what the regenerate-machine-id.sh script does and when I need to run it.
Prompt 5
Help me understand the hardware and access requirements before I attempt to reproduce this setup.

Frequently asked questions

What is dual-spark-optimizations?

A configuration project that tunes a fast, two-node serving setup for running a large language model across two connected NVIDIA DGX Spark machines.

What language is dual-spark-optimizations written in?

Mainly Python. The stack also includes Python, vLLM, Docker.

What license does dual-spark-optimizations use?

No license information was found in the README, the underlying model weights carry their own separate usage agreement.

How hard is dual-spark-optimizations to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is dual-spark-optimizations for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.