-
Notifications
You must be signed in to change notification settings - Fork 903
[grpo] Support PYTORCH_CUDA_ALLOC_CONF environment variable #5897
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
Conversation
Summary of ChangesHello @hjh0119, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the GRPO trainer's memory management capabilities by integrating support for PyTorch's PYTORCH_CUDA_ALLOC_CONF environment variable. It introduces a mechanism to dynamically control CUDA expandable memory segments, which can help prevent out-of-memory errors and improve memory utilization, especially when working with vLLM. The changes ensure that memory allocation behavior can be fine-tuned during specific operational phases, such as vLLM engine setup and inference, while respecting user-defined environment settings. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request introduces support for toggling expandable_segments
in PyTorch's CUDA allocator via the PYTORCH_CUDA_ALLOC_CONF
environment variable, aiming to reduce OOM errors in GRPO training with vLLM. My review focuses on the robustness of this new state management. The current implementation manually toggles the setting, which is not exception-safe and could leave the environment in an inconsistent state. I have provided suggestions to use try...finally
blocks to guarantee that the allocator settings are always restored. Additionally, I've noted a minor code redundancy in the new utility function.
>>> set_expandable_segments(True) # Enable to help with OOM issues | ||
>>> set_expandable_segments(False) # Disable for more predictable memory usage | ||
""" | ||
global _EXPANDABLE_SEGMENTS_SET |
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.
Support the environment variable PYTORCH_CUDA_ALLOC_CONF="expandable_segments:True" in GRPO when using vLLM