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

[Misc]: Implement CPU/GPU swapping in BlockManagerV2 #3834

Merged
merged 39 commits into from
Jun 3, 2024

Conversation

Kaiyang-Chen
Copy link
Contributor

@Kaiyang-Chen Kaiyang-Chen commented Apr 3, 2024

A draft PR for #3666, supporting CPU-GPU swapping for Block Manager V2.


PR Checklist (Click to Expand)

Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

  • [Bugfix] for bug fixes.
  • [CI/Build] for build or continuous integration improvements.
  • [Doc] for documentation fixes and improvements.
  • [Model] for adding a new model or improving an existing model. Model name should appear in the title.
  • [Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
  • [Kernel] for changes affecting CUDA kernels or other compute kernels.
  • [Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
  • [Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
  • [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

  • We adhere to Google Python style guide and Google C++ style guide.
  • Pass all linter checks. Please use format.sh to format your code.
  • The code need to be well-documented to ensure future contributors can easily understand the code.
  • Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
  • Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes

Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.

What to Expect for the Reviews

The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

  • After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
  • After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
  • After the review, the reviewer will put an action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
  • Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You

Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Copy link
Collaborator

@cadedaniel cadedaniel left a comment

Choose a reason for hiding this comment

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

Thanks for working on this. I'm leaving some early feedback.

vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block/block_table.py Outdated Show resolved Hide resolved
vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block/cpu_gpu_block_allocator.py Outdated Show resolved Hide resolved
@cadedaniel
Copy link
Collaborator

Will take another pass tomorrow

@cadedaniel
Copy link
Collaborator

I passed through the code. I think this PR is mixing the abstraction boundaries too much. I wrote out some pseudocode for a better way of using the existing APIs -- take a look.

https://docs.google.com/document/d/157VCEOs5EIB1aztD51ZrT2RvdjxMx1spazyBM4LS4aQ/edit

@Kaiyang-Chen
Copy link
Contributor Author

Hi Cade, It's ready for review. @cadedaniel

@cadedaniel
Copy link
Collaborator

OK, will take a look thurs or fri this week

Copy link
Collaborator

@cadedaniel cadedaniel left a comment

Choose a reason for hiding this comment

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

Looking a lot better! Thanks for improving the PR.

Some missing things:

  • We'll need e2e tests which verify swapping works and produces correct results. You can basically copy these tests and simply enable preemption by swap instead of by compute.
  • The unit test in this PR is pretty narrow in its coverage. I suggest writing the test at a lower level (at the BlockAllocator level), so that you can more easily test num_lookhead=[0, 2] and type=[prefix, naive].

vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block/prefix_caching_block.py Show resolved Hide resolved
vllm/core/block/cpu_gpu_block_allocator.py Show resolved Hide resolved
vllm/core/block_manager_v2.py Outdated Show resolved Hide resolved
vllm/core/block/block_table.py Outdated Show resolved Hide resolved
tests/core/block/test_block_manager_v2.py Show resolved Hide resolved
tests/core/block/test_block_manager_v2.py Outdated Show resolved Hide resolved
Copy link
Collaborator

@cadedaniel cadedaniel left a comment

Choose a reason for hiding this comment

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

Is it ready for review again?

@Kaiyang-Chen
Copy link
Contributor Author

Is it ready for review again?

Nope, still working on the test, will push the new version later today or tmr and notify you. Thanks for the attention!

@Kaiyang-Chen
Copy link
Contributor Author

@cadedaniel Hi cade, i think it's ready for another round of review. One small point is currently the preemption_mode parameter in _preempt() are default to RECOMPUTE and never be passed in. Add some tiny changes around that to support testing preemption by swapping, should we add those in an separate MR?

@Kaiyang-Chen
Copy link
Contributor Author

retrying

Hi Cade, can you help to retry the last failed test one more time? Thanks!

@cadedaniel
Copy link
Collaborator

retried

@Kaiyang-Chen
Copy link
Contributor Author

retried

@cadedaniel TY! I think all tests are passed now.

@Kaiyang-Chen
Copy link
Contributor Author

@cadedaniel Hi cade, solved the new conflicts. Can you help to retry and get it merged? TY!

@cadedaniel
Copy link
Collaborator

thanks @Kaiyang-Chen . i was out last week. I will get this merged this week, thanks for all your work!

@Kaiyang-Chen
Copy link
Contributor Author

@cadedaniel resolve the conflicts again. Can we merge this now?

@cadedaniel cadedaniel enabled auto-merge (squash) May 30, 2024 00:12
@cadedaniel
Copy link
Collaborator

Enabled auto merge

auto-merge was automatically disabled May 30, 2024 14:19

Head branch was pushed to by a user without write access

@Kaiyang-Chen
Copy link
Contributor Author

Enabled auto merge

@cadedaniel It seems this cannot be auto merged because I don't have write access to the repo?

@cadedaniel cadedaniel merged commit 10c38e3 into vllm-project:main Jun 3, 2024
64 checks passed
@cadedaniel
Copy link
Collaborator

Done! thanks again @Kaiyang-Chen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants