explaingit

tonyd2wild/glm5.2-2bit-2-dgx-spark--21.5tok-s

Analysis updated 2026-05-18

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

TLDR

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.

Mindmap

mindmap
  root((GLM5.2 2bit DGX Spark))
    What it does
      Runs 753B model on 2 nodes
      2-bit quantization
      Field report of fixes
    Tech stack
      Python
      vLLM
      CUDA
      NCCL
    Use cases
      Multi-node LLM deployment
      Debugging vLLM failures
      Benchmark reference
    Audience
      ML infra engineers
      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 build with it?

USE CASE 1

Learn how to run a 753B parameter LLM in 2-bit quantization across two GPU nodes.

USE CASE 2

Debug multi-node vLLM deployment failures like path mismatches and missing model shards.

USE CASE 3

Reference real benchmark numbers for GLM-5.2 running on DGX Spark hardware.

USE CASE 4

Apply the included patches to fix known issues in the upstream vLLM-Moet fork.

What is it built with?

PythonvLLMCUDANCCLRay

How does it compare?

tonyd2wild/glm5.2-2bit-2-dgx-spark--21.5tok-schandar-lab/semantic-wmdjlougen/hive
Stars303030
LanguagePythonPythonPython
Setup difficultyhardhardeasy
Complexity5/55/53/5
Audienceops devopsresearcherdeveloper

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 NVIDIA DGX Spark machines, hundreds of gigabytes of model shards, and applying several patches to a specific vLLM fork.

No license is mentioned in the README, so reuse terms are unclear.

In plain English

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.

Copy-paste prompts

Prompt 1
Walk me through the ten failure modes documented in this repo and how each was fixed.
Prompt 2
Help me verify my model checkpoint has no missing shards using tools/tensor_audit.py from this repo.
Prompt 3
Explain why this setup uses 2-bit quantization for experts but keeps attention in FP8.
Prompt 4
Help me apply the patches in this repo to my own vLLM-Moet deployment.

Frequently asked questions

What is glm5.2-2bit-2-dgx-spark--21.5tok-s?

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.

What language is glm5.2-2bit-2-dgx-spark--21.5tok-s written in?

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

What license does glm5.2-2bit-2-dgx-spark--21.5tok-s use?

No license is mentioned in the README, so reuse terms are unclear.

How hard is glm5.2-2bit-2-dgx-spark--21.5tok-s to set up?

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

Who is glm5.2-2bit-2-dgx-spark--21.5tok-s for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.