tonyd2wild/glm5.2-2bit-2-dgx-spark--21.5tok-s — explained in plain English
Analysis updated 2026-05-18
Learn how to run a 753B parameter LLM in 2-bit quantization across two GPU nodes.
Debug multi-node vLLM deployment failures like path mismatches and missing model shards.
Reference real benchmark numbers for GLM-5.2 running on DGX Spark hardware.
Apply the included patches to fix known issues in the upstream vLLM-Moet fork.
| tonyd2wild/glm5.2-2bit-2-dgx-spark--21.5tok-s | chandar-lab/semantic-wm | djlougen/hive | |
|---|---|---|---|
| Stars | 30 | 30 | 30 |
| Language | Python | Python | Python |
| Setup difficulty | hard | hard | easy |
| Complexity | 5/5 | 5/5 | 3/5 |
| Audience | ops devops | researcher | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires two NVIDIA DGX Spark machines, hundreds of gigabytes of model shards, and applying several patches to a specific vLLM fork.
This repository is a field report from someone who managed to run a massive AI language model, GLM-5.2, which has 753 billion parameters, on a pair of NVIDIA DGX Spark computers connected together. Getting a model this large to run at all normally needs far more hardware than two machines, so the author shrank the model's memory footprint by compressing most of its weights down to 2 bits per number, a technique called quantization, while keeping certain sensitive parts of the model at higher precision so the output stays coherent rather than turning into gibberish. The repository itself is not the core engineering work. That credit goes to an existing open source fork and a set of pre-processed model files that others built and published. What this repo adds is the practical experience of getting that existing recipe to actually work on a real two machine setup, plus the small patches and scripts the author wrote to fix problems along the way. The README documents measured speeds around 14 to 15 tokens generated per second on tasks like writing code, solving math problems, and writing prose, with later improvements reaching over 21 tokens per second at peak. It also documents ten separate problems the author ran into while setting this up, such as the two machines having different home folder paths that broke file lookups, missing environment variables, a bug in how a fallback path handled a certain kernel setup, and, most notably, output that looked fine at a glance but was actually gibberish because one required file, containing a small but essential piece of the model, had not been downloaded. The author closes with three lessons for anyone attempting something similar: keep file paths consistent across machines, verify that every needed model file downloaded successfully before assuming garbled output means something else is broken, and check specific markers in the startup logs rather than only watching for outright errors. This project is aimed at people already working with large scale AI model deployment on specialized hardware. It has 30 stars and does not state a license.
A field report documenting how to run a 753 billion parameter AI model in 2-bit compression across two NVIDIA DGX Spark machines, with fixes for ten real deployment failures.
Mainly Python. The stack also includes Python, vLLM, CUDA.
No license is mentioned in the README, so reuse terms are unclear.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.