Discover and explore top open-source AI tools and projects—updated daily.
JustVuggMassive MoE models on everyday machines
New!
Top 18.5% on SourcePulse
Summary
This project addresses the significant challenge of running massive 744B parameter Mixture-of-Experts (MoE) models, such as GLM-5.2, on consumer-grade hardware with limited RAM. It delivers a pure C, zero-dependency engine that streams model experts from disk, enabling frontier LLMs to run on machines with approximately 25 GB of RAM. The primary benefit is democratizing access to extremely large language models by drastically reducing hardware barriers.
How It Works
The core innovation lies in a single C file engine that loads the dense components of GLM-5.2 (around 9.9 GB) into RAM while streaming the ~370 GB of sparse experts from disk on demand. It employs aggressive int4 quantization, MLA attention with a compressed KV-cache, a DeepSeek-style router, and native MTP speculative decoding. This design minimizes the active memory footprint, making colossal models runnable through efficient disk I/O and optimized C kernels.
Quick Start & Requirements
cd c && ./setup.sh. Inference is initiated via COLI_MODEL=/path/to/model ./coli chat. Model conversion from FP8 to the engine's int4 format requires Python with torch, safetensors, huggingface_hub, and numpy.jlnsrk/GLM-5.2-colibri-int4).Highlighted Details
coli serve.Maintenance & Community
This project is described as a "one-person project." Development is supported through community contributions via GitHub issues, particularly for providing benchmark numbers from diverse hardware, sponsoring development, or donating hardware. No dedicated community channels like Discord or Slack are explicitly mentioned.
Licensing & Compatibility
Limitations & Caveats
Performance is heavily dependent on disk I/O, leading to slow cold start token generation (~0.05–0.1 tok/s on the developer's hardware). The experimental CUDA backend is not fully optimized for streaming experts and has specific requirements. The accuracy impact of int4 quantization requires further comprehensive benchmarking. The API is currently text-only, lacking support for advanced features like tools or multimodal inputs. Acceptable performance necessitates a local NVMe drive.
18 hours ago
Inactive
zhihu
EricLBuehler