vllm-project/vllm

A high-throughput and memory-efficient inference and serving engine for LLMs

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on June 5th, 2024
Created on February 9th, 2023
Open Issues & Pull Requests: 8,695 (+0)
GitHub issues: Enabled
Number of forks: 23,251
Total Stargazers: 93,566 (+3)
Total Subscribers: 599 (+0)

Repository Insights (GitGenius)

Maintainer activity

234 people did triage or write work on this repository in the last 12 months.

At least 3% of vllm's 234 maintainers work at Red Hat. 116 say where they work, and 8 of those are Red Hat.

vLLM owns this repository. 1 of its person did this work here, and is not included above.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Almost all tracked open issues have seen activity in the last three months. 67% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2,593
New in 7 days: 213
Closed in 7 days: 205
Avg open age: 51 days
Stale 30+ days: 1,328
Stale 90+ days: 73

Recent activity

Opened in 7 days: 196
Closed in 7 days: 178
Comments in 7 days: 501
Events in 7 days: 1,360

Top labels

  • bug (8,149)
  • stale (7,391)
  • feature request (2,169)
  • usage (1,704)
  • RFC (680)
  • rocm (639)
  • performance (536)
  • installation (477)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

The core purpose of vLLM is to provide fast and easy-to-use LLM inference and serving capabilities. Performance optimization is central to the project's design, achieved through several key technical innovations. PagedAttention enables efficient management of attention key and value memory, while continuous batching of incoming requests and chunked prefill strategies maximize throughput. The engine supports fast and flexible model execution via piecewise and full CUDA and HIP graphs. vLLM implements extensive quantization support including FP8, MXFP8/MXFP4, NVFP4, INT8, INT4, GPTQ, AWQ, GGUF, and compressed-tensors formats. Optimized attention kernels such as FlashAttention, FlashInfer, TRTLLM-GEN, FlashMLA, and Triton implementations further enhance performance, alongside optimized GEMM and Mixture-of-Expert kernels using CUTLASS and CuTeDSL. The system also incorporates speculative decoding techniques including n-gram, suffix, EAGLE, and DFlash approaches, plus automatic kernel generation through torch.compile.

vLLM supports over 200 model architectures from Hugging Face, spanning decoder-only LLMs like Llama and Qwen, Mixture-of-Expert models such as Mixtral and DeepSeek-V3, hybrid attention and state-space models like Mamba, multi-modal models including LLaVA and Qwen-VL, and embedding and retrieval models. The platform provides flexible deployment options through tensor, pipeline, data, expert, and context parallelism for distributed inference, alongside support for multiple hardware backends including NVIDIA GPUs, AMD GPUs, x86/ARM/PowerPC CPUs, Google TPUs, Intel Gaudi, IBM Spyre, Huawei Ascend, and Apple Silicon.

The project maintains an OpenAI-compatible API server alongside Anthropic Messages API and gRPC support, enabling seamless integration into existing workflows. Additional features include structured output generation via xgrammar or guidance, tool calling and reasoning parsers, efficient multi-LoRA support for both dense and MoE layers, and streaming output capabilities.