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.
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
[Hardware][CPU] Multi-LoRA implementation for the CPU backend #11100
[Hardware][CPU] Multi-LoRA implementation for the CPU backend #11100
Changes from 28 commits
c8a8c5b
3545ac1
2b3c650
cc0bd6c
dc9091a
410b746
8eab6a6
5dfcf62
651dc04
d1026bb
2840445
41c518f
abb03e5
d212fc9
dcb1794
3a684b8
c9b9f63
acdb4e3
cfa082f
8eaf7ec
bd54243
21c3799
aeaf078
61c42cf
0d19f03
5af9cbb
202aca3
76444f4
64c700f
06399bc
69eb3dc
e208468
d8cb9af
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@DarkLight1337 Are our CPU vendor willing to provide hardware testing for these? Who should we contact?
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.
I remember there is no numa node restriction for CPU TP, so I think we can just change
VLLM_CPU_OMP_THREADS_BIND=48-92
to something likeVLLM_CPU_OMP_THREADS_BIND=48-70|71-92
to enable TP, even if these cores are on same numa node.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.
My bad, I meant to ask if the CPU LoRA testing should be placed here. If so, we might need to contact the CPU vendor?
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.
@jeejeelee Hi, I think it may be easier to run the offline lora case? Thus we don't need to download the weights file
https://github.com/vllm-project/vllm/blob/main/.buildkite/run-cpu-test.sh#L33
https://github.com/vllm-project/vllm/blob/main/examples/multilora_inference.py
CC @bigPYJ1151
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.
@zhouyuan Do you mean adding
multilora_inference.py
to https://github.com/vllm-project/vllm/blob/main/.buildkite/run-cpu-test.sh#L33?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.
Yes, the target is to enable a test to verify the lora code path on CPU backend