explaingit

miaai-lab/glm-5.2-nvfp4-aqlm-triple-dgx-sparks

Analysis updated 2026-07-26

34ShellAudience · ops devopsComplexity · 5/5Setup · hard

TLDR

Shell scripts to run a compressed 272 GB language model across three linked NVIDIA machines as a single API endpoint, using specialized compression to fit within tight memory limits.

Mindmap

mindmap
  root((repo))
    What it does
      Runs GLM-5.2 model
      Spans three machines
      Single API endpoint
    Tech stack
      Shell scripts
      Docker containers
      vLLM fork
      Ray coordination
    Hardware needs
      Three DGX Sparks
      Fast RoCE network
      280GB storage per node
    Performance
      380K token context
      13 to 22 tok per sec
      121GiB memory per node
    Setup gotchas
      Disable earlyoom utility
      39GB container image
      Tight memory limits

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

Serve a massive language model across three linked machines without buying one giant server.

USE CASE 2

Run the GLM-5.2 model with NVFP4 and AQLM compression on DGX Spark hardware.

USE CASE 3

Expose a single text-generation API endpoint backed by a multi-node setup.

What is it built with?

ShellDockervLLMRayNCCLCUDA

How does it compare?

miaai-lab/glm-5.2-nvfp4-aqlm-triple-dgx-sparksgarfieldttt/pve-disk-shrinksoroushyasini/proxysmith
Stars343434
LanguageShellShellShell
Setup difficultyhardmoderatemoderate
Complexity5/54/53/5
Audienceops devopsops devopsops devops

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

How do you get it running?

Difficulty · hard Time to first run · 1day+

Requires three NVIDIA DGX Spark machines with Docker, fast RoCE networking, 280 GB storage per node, SSH access, and a specific NCCL version.

The explanation does not specify a license for this repository.

In plain English

This repository provides a set of shell scripts and configuration files for running a very large language model, GLM-5.2, across three NVIDIA DGX Spark machines working together as one unit. The project is built by Mia's AI Lab and targets a specific compressed version of the model that uses two techniques, called NVFP4 and AQLM, to shrink its size from a much larger original down to about 272 GB on disk. This compression is what makes it possible to fit and run the model across three smaller linked machines instead of a single massive server. The setup uses a customized fork of an existing serving program called vLLM. The standard version of vLLM does not understand this particular hybrid compressed model, so the fork adds the specific code paths needed to load and run it correctly. The three DGX Spark nodes communicate over a fast network link called RoCE, and the scripts handle distributing the model weights, starting the coordination layer called Ray, and launching the serving process. The result is a single API endpoint on port 8888 that can accept text requests. The README reports measured performance from a live three node setup. With the default configuration, the system supports a context window of roughly 380,000 tokens, which refers to how much text the model can consider in a single conversation or request. The key value cache, a memory area the model uses to track context during generation, is pinned at 12 GiB per node. This allows a pool of about 386,688 tokens. Reported decode speed ranges from around 13 to 22 tokens per second depending on the content. Memory usage is very tight, with each node sitting close to its 121 GiB limit and sometimes spilling into swap. The README strongly recommends disabling a system utility called earlyoom on all three machines before starting. Because memory is so constrained, earlyoom can mistakenly kill background processes during a critical setup phase called CUDA graph capture, causing failures that look like graphics memory errors but are actually caused by the host system. The project provides shell commands to stop and verify this utility. Requirements include three DGX Spark machines with Docker installed, fast networking between them, SSH access from a head node to two workers, at least 280 GB of free storage per node, and a specific version of a networking library called NCCL. The quick start process involves cloning the repository, editing a configuration file with network addresses and paths, pulling a prebuilt 39 GB container image, downloading the model weights, and running a few scripts in sequence. A start script automates most of the work, checking for missing pieces and launching the Ray coordination layer and the vLLM serving process. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Help me edit the configuration file for GLM-5.2-NVFP4-AQLM-Triple-DGX-Sparks, I need to fill in network addresses and storage paths for three DGX Spark machines.
Prompt 2
I keep getting CUDA graph capture errors when launching the multi-node GLM-5.2 setup. How do I disable earlyoom on all three machines and verify it worked?
Prompt 3
My DGX Spark nodes are spilling into swap and running out of memory during GLM-5.2 inference. How can I tune the KV cache size or context window to fit within 121 GiB per node?
Prompt 4
Write a curl command to send a text generation request to the GLM-5.2 API endpoint running on port 8888 after the multi-node setup is live.

Frequently asked questions

What is glm-5.2-nvfp4-aqlm-triple-dgx-sparks?

Shell scripts to run a compressed 272 GB language model across three linked NVIDIA machines as a single API endpoint, using specialized compression to fit within tight memory limits.

What language is glm-5.2-nvfp4-aqlm-triple-dgx-sparks written in?

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

What license does glm-5.2-nvfp4-aqlm-triple-dgx-sparks use?

The explanation does not specify a license for this repository.

How hard is glm-5.2-nvfp4-aqlm-triple-dgx-sparks to set up?

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

Who is glm-5.2-nvfp4-aqlm-triple-dgx-sparks for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.