Skip to content
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

[6/N] torch.compile rollout to users #10437

Merged
merged 6 commits into from
Nov 19, 2024

Conversation

youkaichao
Copy link
Member

@youkaichao youkaichao commented Nov 19, 2024

the user interface:

command line:

short: -O 0/1/2/3
long: --compilation-config json_string

vllm.LLM:

users can construct CompilationConfig object directly, and pass compilation_config=obj .

the first roll out will only roll out 3 levels, more fine-grained control will come later as we stabilize them.

documentation on how to use and the design doc will come later.

Signed-off-by: youkaichao <[email protected]>
Copy link

👋 Hi! Thank you for contributing to the vLLM project.
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 do one of these:

  • Add ready label to the PR
  • Enable auto-merge.

🚀

Signed-off-by: youkaichao <[email protected]>
@@ -868,6 +869,16 @@ def add_cli_args(parser: FlexibleArgumentParser) -> FlexibleArgumentParser:
help="Override or set the pooling method in the embedding model. "
"e.g. {\"pooling_type\": \"mean\", \"normalize\": false}.'")

parser.add_argument('--compilation-config',
'-O',
Copy link
Member Author

Choose a reason for hiding this comment

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

I want to mimic the convention of traditional compiler, -O 3 is the most optimized level.

Signed-off-by: youkaichao <[email protected]>
Signed-off-by: youkaichao <[email protected]>
Signed-off-by: youkaichao <[email protected]>
Signed-off-by: youkaichao <[email protected]>
@youkaichao youkaichao marked this pull request as ready for review November 19, 2024 01:22
@youkaichao youkaichao changed the title [7/N] torch.compile rollout to users [6/N] torch.compile rollout to users Nov 19, 2024
'interpreted as the optimization level.\n'
'NOTE: level 0 is the default level without '
'any optimization. level 1 and 2 are for internal '
'testing only. level 3 is the recommended level '
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe add that this (levels 1 and 2) could change in the future - if we actually have multiple optimization levels, we can use O1 and O2 and move the internal levels somewhere else

Copy link
Member Author

Choose a reason for hiding this comment

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

our optimization is actually not well graded as levels. they appear as complicated configs. I would keep only levels 0/1/2/3 , and recommend using 3 for users.

@youkaichao youkaichao added the ready ONLY add when PR is ready to merge/full CI is needed label Nov 19, 2024
@youkaichao youkaichao merged commit 803f37e into vllm-project:main Nov 19, 2024
60 of 64 checks passed
@youkaichao youkaichao deleted the remove_select_and_init branch November 19, 2024 18:09
Copy link
Collaborator

@mgoin mgoin left a comment

Choose a reason for hiding this comment

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

+1 for -O :)

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants