Tag: GLM-5.3-Flash
-
TensorFold 1.0.0 and Multi-Model gr8: Two Release Notes Date the Desk-Side Stack
by Chris DePuy, 650 Group / November 3, 2026. On November 2, the TensorFold Mac application and the gr8 cluster stack, two community inference projects this blog has followed all autumn, published release notes that move this hardware tier toward installed software. Ash Hart, the maintainer of the TensorFold Mac application, announced version 1.0.0, “our…
-
New TensorFold LLM Model Serving Software Dramatically Improves Decode Speed on Macs and Sparks
by Chris DePuy, 650 Group / September 27, 2026 Two repositories shipped from one maintainer this week and made the same promise in two different places. On September 25 and 26, a developer publishing under the name Ash Hart released TensorFold, a local inference engine for Apple Silicon and NVIDIA GPUs, and Imprint, a tool…
-
New NVFP4 Checkpoints on Four DGX Sparks: The Results
Between September 9 and September 16, NVIDIA published first-party NVFP4 checkpoints for two frontier open-weight models, both MIT-licensed. One is a build of Z.ai’s GLM-5.3-Flash; the other is a build of DeepSeek’s DeepSeek-V4.1-Flash. Both labs produced them with NVIDIA Model Optimizer and validated both on rack-mount Blackwell silicon rather than on the desk. That distinction…
-
GLM-5.3-Flash on a Single DGX Spark: Three Community Quantizations Fit Where the Vendor’s Does Not
by Chris DePuy / September 13, 2026 On September 9, NVIDIA published an official NVFP4 quantization of Z.ai’s GLM-5.3-Flash. Its Model Optimizer recipe leaves the key-value cache at FP8 and compresses only the linear layers inside the transformer blocks — the sparse-MoE shared experts and the dense MLP — from 16 bits down to 4,…
-
GLM-5.3-Flash Day Two: DFlash 2 Attacks the Decode Path While 1M-Context KV Moves Onto Two DGX Sparks
by Chris DePuy / August 28, 2026 A day after Z.ai opened weights on GLM-5.3-Flash, the desk-side community pushed the model past what I thought was its practical limit on small hardware. Two bottlenecks — the decode path and the KV cache — were attacked in parallel, and both moved in the same 24 hours.…
