Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: Support storing CUDAGraphs for different input profiles#3792

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
peri044 wants to merge2 commits intomain
base:main
Choose a base branch
Loading
fromsession_cudagraph

Conversation

@peri044
Copy link
Collaborator

Description

Currently, CUDAGraphs get reset when a different inputs are observed. Instead store a cudagraph per input shape key. This is especially important in LLM inference (where prefill and decode have different input shapes)

Fixes # (issue)

Type of change

Please delete options that are not relevant and/or add your own.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project (You can use the linters)
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas and hacks
  • I have made corresponding changes to the documentation
  • I have added tests to verify my fix or my feature
  • New and existing unit tests pass locally with my changes
  • I have added the relevant labels to my PR in so that relevant reviewers are notified

@github-actionsgithub-actionsbot added component: api [Python]Issues re: Python API component: runtime component: dynamoIssues relating to the `torch.compile` or `torch._dynamo.export` paths labelsAug 25, 2025
@peri044peri044 marked this pull request as draftAugust 25, 2025 19:26
@peri044peri044 requested a review fromkeehyunaAugust 25, 2025 19:26
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@narendasannarendasanAwaiting requested review from narendasan

@keehyunakeehyunaAwaiting requested review from keehyuna

Assignees

No one assigned

Labels

cla signedcomponent: api [Python]Issues re: Python APIcomponent: dynamoIssues relating to the `torch.compile` or `torch._dynamo.export` pathscomponent: runtime

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@peri044

[8]ページ先頭

©2009-2025 Movatter.jp