A user shares a Docker configuration for running GLM-5.2-FP8 on HGX-H200 hardware using SGLang. The setup achieves 262k context length and 70 tokens per second with 8 tensor parallelism, using a memory fraction of 0.83. The user notes that vLLM official recipes do not work on H200 due to KV cache FP8 quantization limitations on the DSV3 architecture.
GLM-5.2-FP8 HGX-H200 SGLang Docker Deployment Config
GLM 5.2 Q1_S vs Qwen 27B Q8: A Local LLM Comparison
An amateur comparison on consumer hardware demonstrates that the heavily quantized GLM-5.2 (Q1_S) outperforms the higher-bit Qwen 3.6 27B (Q8) in a complex coding task, despite significantly slower inference speeds.
High-quality GLM-5.2 Quant on 4x DGX Spark - Guide, Results, and Comps
The author demonstrates running the GLM-5.2 NVFP4 model on four NVIDIA GB10 DGX Spark nodes with a 128K context window, achieving usable serving performance through aggressive system optimization.
GLM-5.2 Breakout and Open-Model Progress Highlighted
Zhipu's GLM-5.2 emerged as the top open-weight model, praised for its frontier-adjacent performance in daily use, with improvements in coding tasks and reduced 1M-token inference cost via IndexShare. It outperformed other open models in agentic knowledge work benchmarks, reaching 1266 Elo in Artificial Analysis' AA-Briefcase test, though only 3% of tasks were fully satisfied by top models, indicating persistent challenges in real-world long-horizon agent performance.
GLM-5.2 Beats Gemini and GPT-5.4 in Coding but Is Inefficient
GLM-5.2 surpasses GPT-5.4 and the entire Gemini lineup in coding performance on the DeepSWE benchmark. However, it requires significantly more output tokens, making it substantially less efficient in terms of cost-per-task compared to models like GPT-5.5 and Claude Opus 4.8.
GLM 5.2 Achieves 98% Max Intelligence with Less Than Half Tokens
GLM 5.2 demonstrates 98% of maximum intelligence in coding tasks using less than half of its total token budget, according to a technical report by z_ai. The model's reasoning efficiency has improved significantly, with token usage increasing from 16.7k to 36.7k between GLM 5.1 and GLM 5.2, though high-level settings may strain local hardware performance.