ZICQ
中 Log in / Sign up
ZICQ Info LLMs & Foundation Models #Blockway #Agens Volundr #Long-context #Efficient Inference #Localized Deployment

Blockway Releases Agens Volundr 32B v1: Enhanced Inference Efficiency and Localized Execution

Avatar of Mr.Xu

By Mr.Xu Community Post

Published:

中文阅读 (Chinese) English Version

Summary:Blockway has released Agens Volundr 32B v1, addressing user feedback by reducing repetition loops, increasing reasoning step lengths, and introducing session continuation. The team also open-sourced the Agens Engine inference engine, enabling the model to run within a 16GB memory budget with a context length of up to 262K tokens (validated up to 239K). The engine offers significant performance improvements, such as a 1.4-1.8x increase in decoding speed. While the release demonstrates potential i


Core Breakthroughs

Blockway has released Agens Volundr 32B v1, focusing on addressing user feedback from the preview version. Key improvements include:

  1. Reduced Repetition Loops: Repetition loops in SWE-bench tasks decreased from 36/50 to 0/50.
  2. Increased Reasoning Step Lengths: The median reasoning step length increased from 32K to 120 tokens, with the longest step reaching 12K.
  3. Session Continuation: Introduced through SGLang build, allowing follow-up turns to reuse the model's state instead of re-prefilling, resulting in a 2.9x speedup in subsequent dialogues.

Technical Mechanism Analysis

Agens Volundr 32B v1 employs a hybrid architecture where 54 out of 72 layers maintain a fixed-size state instead of a traditional KV cache. The team has open-sourced the Agens Engine inference engine, which is specifically designed for this architecture and can handle up to 262K tokens of context within a 16GB memory budget (validated up to 239K). Key features include:

  • Performance Improvements: Agens Engine is 1.4-1.6x faster than the SGLang build on the same GPU and INT4 weights, and up to 1.8x faster on code reasoning tasks.
  • Multimodal Support: Supports chat, code, agent, and JSON modes, with decoding speeds increased to 86, 113, 121, and 199 tok/s, respectively.
  • Resource Optimization: Only 18 layers retain the KV cache, making long-context processing more efficient.

Engineering Trade-offs and Benchmark Performance

While Agens Volundr 32B v1 excels in several areas, there are some trade-offs:

  • Reduced Precision: At INT4 quantization, GPQA scores dropped from 80.3 to 73.7, and HumanEval from 73.8% to 73.2%.
  • Hardware Limitations: Requires NVIDIA drivers and CUDA 12.9, at least 32GB host RAM, and Linux OS.
  • Model Size: Weight downloads are 25GB, which may pose storage and bandwidth challenges.

In benchmark tests, Agens Volundr 32B v1 improved from 22/50 to 27/50 in SWE-bench tasks, from 89/120 to 92/120 in τ²-bench, from 63.4 to 67.9 in LiveCodeBench v6, and from 76.7 to 80.0 in AIME 2025.

Developer Implementation and Deployment Recommendations

Agens Volundr 32B v1 is suitable for applications requiring efficient long-context processing and fast inference. Here are some deployment recommendations:

  • Hardware Requirements: Ensure the use of NVIDIA GPUs, CUDA 12.9, and at least 32GB host RAM.
  • Software Environment: Use Docker to run the pre-built engine image and mount the model and drafter directories.
  • Performance Optimization: For applications needing higher performance, consider using larger GPUs or optimizing the inference workflow.

Conclusion

Agens Volundr 32B v1 demonstrates significant advantages in long-context processing and efficient inference, but it also involves trade-offs such as reduced precision and hardware limitations. For applications requiring localized deployment and efficient inference, this version is a worthy consideration.


Source: Reddit r/LocalLLaMA (2026-10-18)

— END —

Tags: #Blockway #Agens Volundr #Long-context #Efficient Inference #Localized Deployment

Editorial & Fact-Checking Note: This article is compiled from primary research, official release documentation, and source papers by the ZICQ Newsroom pipeline with automated entity verification and human editorial review. If you notice any technical inaccuracy, please submit a correction via our corrections policy or email our editorial desk directly.

Community Comments

Loading live comments and annotations…