Repository navigation
ggml-cuda: drop the CUDA graph cache count cap, as upstream does #253
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
danielhanchen
merged 2 commits into
carry/superseded-pin-optimizations
from
fix/cuda-graph-cache-no-cap
Oct 9, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When CUDA or HIP graphs are enabled in a server and clients generate many distinct prompt or batch shapes within the 10-second retention window, each shape and tensor-split segment can now add a cache entry, including a full
node_propsvector and potentially a graph executable after warmup. The time-based sweep does not impose a count or byte limit, so a sufficiently fast burst can exhaust host or device memory before any entry becomes old enough to evict; it also cannot release stale entries while the server is idle because it only runs fromcuda_graph(). Keep a bound sized for tensor-split workloads, or avoid shape-keying one-off prefill graphs.Useful? React with 👍 / 👎.