SShortSingh.
Back to feed

GLM-5.2: How to Run the 753B MoE Model Locally with Unsloth Quantization

0
·1 views

GLM-5.2 is a 753-billion-parameter Mixture-of-Experts model that activates only 40 billion parameters per token, making its compute cost comparable to a 40B model while requiring up to 1.51 TB of RAM at full BF16 precision. Running it locally at full precision is impractical for most users, as even eight H100 GPUs provide only around 640 GB of memory. Unsloth's dynamic GGUF quantizations on Hugging Face address this by allocating more bits to critical layers and fewer to less important ones, preserving quality better than traditional uniform quantization. The UD-Q4_K_XL variant at 467 GB is considered the quality sweet spot, while UD-Q3_K_XL at 343 GB is the recommended minimum for users with four GPUs. For general-purpose tasks not involving code or complex reasoning, Unsloth itself suggests the UD-IQ2_M at 239 GB, which retains 82% Top-1 accuracy relative to the full BF16 model.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

New Research Confirms Einstein's Relativity Shapes Chemical Bonds in Heavy Elements

New research from Brown University, published in July 2026, demonstrates that Einstein's theory of relativity plays a direct role in determining chemical bonding behavior in heavy elements. The study shows that as atomic number increases, electrons in heavy atoms move at speeds significant enough for relativistic effects to alter their energy levels and spatial distribution. These relativistic shifts influence how heavy elements form bonds, explaining certain anomalous chemical properties observed in metals like gold and mercury. The findings provide a clearer theoretical framework for understanding why heavy elements often behave differently from their lighter counterparts in the periodic table.

0
ProgrammingDEV Community ·

Developer builds automated WinPE deployment script to replace manual DISM commands

A developer at a company where third-party imaging tools are restricted turned the limitation into an opportunity by building a custom Windows deployment script from scratch. The solution, called deploy.cmd, consolidates disk partitioning, image application, and bootloader configuration into a single self-contained Batch script running within WinPE. To eliminate manual filename entry errors, the script dynamically scans a directory for .wim files and presents them as a numbered menu using delayed variable expansion. Diskpart instructions are generated on-the-fly into a temporary file, executed silently, and logged for troubleshooting, while bcdboot automatically configures UEFI boot files after imaging. The complete scripts have been published on GitHub for others facing similar enterprise environment restrictions.

0
ProgrammingDEV Community ·

Developer Builds Free AI-Powered RFP Compliance Checker Using Groq and Cloudflare

A developer built a browser-based tool that checks procurement bid responses against specification requirements, flagging compliant, partial, and missing clauses. The tool uses Groq's free-tier API running the Llama 3.3-70B model for inference, with a single Cloudflare Worker serving as the backend. No user accounts, databases, or stored data are involved, keeping ongoing infrastructure costs at zero. The most challenging aspect was engineering a prompt that reliably returns structured JSON across varied procurement document formats, solved by combining a strict JSON schema, explicit response formatting, and a near-zero temperature setting. The developer plans to release additional single-purpose procurement tools in the same series, with a plain-English bid-grader announced as the next project.

0
ProgrammingDEV Community ·

Rust Borrowing Explained: Immutable vs Mutable Access and Why It Matters

Rust's borrowing system controls data access through two forms: immutable borrows for read-only use and mutable borrows for exclusive write access. The core rule is straightforward — multiple readers are allowed, or one writer, but never both simultaneously. This design prevents common bugs such as accidental mutation, stale data reads, and race conditions that are frequent in languages like Python, Java, or C. The borrow checker enforces these access patterns at compile time, making code behavior predictable without requiring runtime checks. Rather than a restriction, Rust's borrowing model is intended as a safety-focused design tool that encourages developers to think clearly about data ownership and access lifecycles.