Skip to content
aiqbench takeChips & Infra

aiqbench analysis

Humming targets a real bottleneck: quantized inference only saves memory and latency if the kernels that run it are efficient across precisions, scaling schemes, and MoE expert loads. The reported gains are vendor-benchmarked, so readers should check them against their own models and GPUs before assuming a speedup. The most practical signals are the breadth of hardware support and whether the library holds up in vLLM deployments.
Sources coveringvLLM Blog, PyTorch, Latent Space, arXiv

Announcing Humming: Fast, Flexible Kernels for Quantized Inference

vLLM Blog16 min read

Introducing Humming, a quantized inference kernel library from Ant Group and the vLLM community, with broad GPU and quantization support, dense and MoE performance results, and vLLM integration.

Ant Group and the vLLM community are open-sourcing Humming, a general-purpose, high-performance kernel library for quantized inference. Humming offers the following features: Broad device support: Supports NVIDIA GPU architectures from Turing onward, along with CUDA-compatible devices such as T-Head's Zhenwu 810E. Extensive quantization support: A unified architecture supports diverse combinations of weight and activation formats for dense and MoE workloads, covering a wide range of integer and floating-point types, bit widths, and scaling schemes. Strong execution performance: Significantly outperforms existing implementations from vLLM Marlin, FlashInfer, and DeepGEMM across many representative workloads. Repository: github.com/vllm-project/humming As models and inference workloads grow, memory capacity, memory bandwidth, and compute costs increasingly constrain deployment. This is especially apparent in MoE models: each token activates only a subset of experts, but the full set of weights still needs to be stored. DeepSeek-V3, for example, has 671 billion parameters, with 37 billion activated per token. Quantization lowers the precision of weights and activations to reduce memory usage and data movement, and can also improve compute efficiency. Quantization requirements vary across models and GPU generations. Common configurations include WNA16, W8A8, W4A8, and W4A4, where W and A specify weight and activation bit widths, and N denotes a variable…

Excerpt shown under the publisher's RSS terms · 200 words · full text and figures are on the publisher's site

Related coverage