git404hub

what is minimax-m3-2x-dgx-spark-36-tok-s fr?

tonyd2wild/minimax-m3-2x-dgx-spark-36-tok-s — explained in plain English

Analysis updated 2026-05-18

39Audience · researcherComplexity · 5/5Setup · hard

tl;dr

A setup guide for running the full 428-billion-parameter MiniMax-M3 language model at 36 tokens per second across two NVIDIA DGX Spark machines.

vibe map

mindmap
  root((repo))
    What it does
      Runs a 428B model on 2 machines
      Compresses weights and memory cache
      Speeds replies with speculative decoding
    Tech stack
      vLLM
      Docker
      NVIDIA DGX Spark
    Use cases
      Serve a huge model on small hardware
      Reproduce published benchmark numbers
      Choose speed vs context length lane
    Audience
      Developers
      Researchers

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 make with this?

VIBE 1

Reproduce a full-size, unpruned MiniMax-M3 deployment on two DGX Spark machines.

VIBE 2

Choose between speed, balanced, or long-context serving configurations.

VIBE 3

Verify published throughput benchmarks on independent hardware.

VIBE 4

Apply patches that fix known build and deployment issues in the original setup.

what's the stack?

vLLMDockerNVIDIA DGX SparkPyTorch

how it stacks up fr

tonyd2wild/minimax-m3-2x-dgx-spark-36-tok-saa2448208027-code/localaihotswapaaronparton2-sketch/swell-event
Stars393939
LanguagePython
Setup difficultyhardmoderate
Complexity5/53/5
Audienceresearcherdevelopergeneral

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

how do i run it?

Difficulty · hard time til it works · 1day+

Requires two NVIDIA DGX Spark machines networked together plus large model downloads and careful build patching.

This repository's own license is not stated, the upstream project it reproduces is MIT licensed, allowing free use and modification.

in plain english

This repository documents how to run the full, unshrunk version of a very large AI language model called MiniMax-M3, which has 428 billion parameters, on a pair of small NVIDIA computers designed for AI work called DGX Sparks, and have it respond at a usable speed of about 36 words per second. Normally a model this size needs much bigger, more expensive hardware, so the project explains the specific tricks used to make it fit and run reasonably fast on two of these smaller machines connected together. The author is upfront that this work builds directly on someone else's published setup rather than starting from scratch. That original work, licensed under MIT, provided the core recipe, and this repository reproduces it on independent hardware, confirms the original speed claims hold up, fixes two build and deployment problems, recovers a configuration the original author had set aside, and documents tricky gotchas encountered along the way. Technically, the model's memory footprint is shrunk using a 4-bit weight compression technique, its short-term memory cache is also compressed to 4 bits, and a smaller helper model predicts likely upcoming words to speed up generation, a technique called speculative decoding. All of this runs through a serving tool called vLLM, split across two machines working together. The project offers three different serving configurations to choose from depending on whether a user wants more speed, more conversation length capacity, or a balance of both, with the balanced option being the one the author has fully verified. Setup involves cloning the original author's code, applying two provided patches to fix build issues, building a Docker container image, downloading the large model files once and copying them between the two machines over a fast network link, then starting the server with a specific configuration file. The README includes exact commands for each of these steps, along with a warning to discard the very first request after starting the server, since it takes about a minute to fully warm up before giving an accurate sense of speed.

prompts (copy fr)

prompt 1
Help me follow tonyd2wild/MiniMax-M3-2x-DGX-Spark-36-tok-s to set up MiniMax-M3 on two DGX Sparks.
prompt 2
Explain how the 4-bit weight and KV cache compression let a 428B model fit on this hardware.
prompt 3
Walk me through applying the two patches before building the Docker image.
prompt 4
Explain the difference between the speed, balanced, and long-context serving lanes.

Frequently asked questions

what is minimax-m3-2x-dgx-spark-36-tok-s fr?

A setup guide for running the full 428-billion-parameter MiniMax-M3 language model at 36 tokens per second across two NVIDIA DGX Spark machines.

What license does minimax-m3-2x-dgx-spark-36-tok-s use?

This repository's own license is not stated, the upstream project it reproduces is MIT licensed, allowing free use and modification.

How hard is minimax-m3-2x-dgx-spark-36-tok-s to set up?

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

Who is minimax-m3-2x-dgx-spark-36-tok-s for?

Mainly researcher.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.