PulseAugur
EN
LIVE 18:53:45

GLM-5.2 NVFP4 achieves 24 tok/s at 128K context after bug fix · 1 source tracked

A user has resolved an issue with the GLM-5.2 NVFP4 model running on four DGX Sparks, achieving approximately 24 tokens per second at a 128K context length. The problem involved a bug in the speculative decoding configuration where the draft model's KV cache and metadata were sharded, but its attention mechanism did not recognize this sharding, leading to incorrect calculations. This bug was fixed by ensuring the `decode_context_parallel_size` was correctly copied during configuration, eliminating the previous trade-off between context length and speed. AI

IMPACT User-level optimization details for a specific model configuration, offering insights into performance tuning.

RANK_REASON User-level technical follow-up on optimizing a specific model configuration.

Read on r/LocalLLaMA →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

GLM-5.2 NVFP4 achieves 24 tok/s at 128K context after bug fix · 1 source tracked

COVERAGE [1]

  1. r/LocalLLaMA TIER_1 English(EN) · /u/llamaCTO ·

    Follow-up: GLM-5.2 NVFP4 on four DGX Sparks — the MTP mystery is solved, and it's now ~24 tok/s at 128K context

    <!-- SC_OFF --><div class="md"><h1>Follow-up: GLM-5.2 NVFP4 on four DGX Sparks — the MTP mystery is solved, and it's now ~24 tok/s at 128K context</h1> <p>This is a follow-up to my earlier post about running GLM-5.2 NVFP4 on 4x DGX Spark at 128K context. Short version of that pos…