Skip to content

[MISC] rename interval to max_recent_requests #14285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

andyxning
Copy link
Contributor

@andyxning andyxning commented Mar 5, 2025

rename interval to max_recent_requests to make the code more readable.

Copy link

github-actions bot commented Mar 5, 2025

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

@mergify mergify bot added the v1 label Mar 5, 2025
@@ -34,12 +34,12 @@ class PrefixCachingMetrics:
"""Metrics for prefix caching with a hit rate of the most recent N requests.

Args:
interval: The number of the most recent requests to aggregate.
max_recent_queries: The number of the most recent requests to aggregate.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It actually "max_recent_requests". We might also need to correct the document...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. PTAL.

@andyxning andyxning force-pushed the rename_interval_to_max_recent_queries branch 2 times, most recently from 5e776b2 to d3cd504 Compare March 6, 2025 02:16
@andyxning andyxning force-pushed the rename_interval_to_max_recent_queries branch from d3cd504 to 4bff1eb Compare March 6, 2025 02:17
@andyxning andyxning changed the title [MISC] rename interval to max_recent_queries [MISC] rename interval to max_recent_requests Mar 6, 2025
@comaniac comaniac enabled auto-merge (squash) March 6, 2025 02:26
@comaniac comaniac added the ready ONLY add when PR is ready to merge/full CI is needed label Mar 6, 2025
@DarkLight1337
Copy link
Member

Can you merge from main to try to resolve the CI failures?

@DarkLight1337
Copy link
Member

Entrypoints tests are failing consistently, PTAL

@comaniac comaniac merged commit fd11a32 into vllm-project:main Apr 26, 2025
42 checks passed
@andyxning andyxning deleted the rename_interval_to_max_recent_queries branch April 27, 2025 02:00
jikunshang pushed a commit to jikunshang/vllm that referenced this pull request Apr 29, 2025
lk-chen pushed a commit to lk-chen/vllm that referenced this pull request Apr 29, 2025
adobrzyn pushed a commit to HabanaAI/vllm-fork that referenced this pull request Apr 30, 2025
RichardoMrMu pushed a commit to RichardoMrMu/vllm that referenced this pull request May 12, 2025
zzzyq pushed a commit to zzzyq/vllm that referenced this pull request May 24, 2025
minpeter pushed a commit to minpeter/vllm that referenced this pull request Jun 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready ONLY add when PR is ready to merge/full CI is needed v1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants