vllm-project/vllm

[Feature]: Better Flashinfer compilation logging

Open

#38246 opened on Mar 26, 2026

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Python (80,034 stars) (16,816 forks)batch import
feature requesthelp wanted

Description

🚀 The feature, motivation and pitch

Sometimes Flashinfer will compile for 10mins without a single log, making it easy to think it's a hang. Would be good to add a progress bar or at least a simple log.

See https://github.com/vllm-project/vllm/issues/38241 for more info. Note that this was without flashinfer-jit-cache installed.

Alternatives

No response

Additional context

No response

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Contributor guide

Tech stack
python
Domain
developer experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Pythonvllm build systemFlashinfer
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the Flashinfer compilation code in the vllm repository, likely in the `csrc` or `flashinfer` integration. Reference issue #38241 for context. Add a progress bar or log statements using Python's logging module or tqdm. Consider checking the build scripts such as `setup.py` or CMake files.