Perf: avoid intermediate tensor allocs via in-place div & optimized top-k flow#8268
Conversation
|
/gemini review |
Summary of ChangesHello, 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 focuses on enhancing the performance and reducing the memory footprint of various trainer modules by optimizing tensor operations. The core change involves replacing out-of-place tensor divisions with in-place operations and restructuring top-k processing to minimize the creation of temporary tensors. These changes aim to make the training process more memory-efficient without altering the numerical results. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
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.
Code Review
This pull request aims to improve performance by avoiding intermediate tensor allocations, primarily by using in-place division and optimizing operation order. While many of the changes effectively achieve this, I've identified two instances where using in-place operations introduces unintended side effects by modifying input tensors. This alters the functions' behavior and could lead to bugs if the calling code reuses these tensors. My review includes suggestions to revert these specific changes to preserve correctness while retaining the other valuable performance optimizations.
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces performance optimizations to the GKD trainers by avoiding intermediate tensor allocations. The changes primarily involve using in-place division (div_) and reordering operations to apply temperature scaling after masking or top-k selection, which reduces memory usage. These optimizations are consistently applied in both swift/megatron/trainers/gkd_trainer.py and swift/rlhf_trainers/gkd_trainer.py. The logic appears sound and the changes align with the performance improvement goals of the PR.
There was a problem hiding this comment.
Code Review
The pull request introduces performance optimizations by avoiding intermediate tensor allocations through the use of in-place division (.div_()) and optimizing the top-k flow in the generalized_jsd_loss and _jsd_topk functions. These changes reduce memory footprint and improve computational efficiency, aligning well with the stated objective of the pull request. The modifications are consistently applied across both swift/megatron/trainers/gkd_trainer.py and swift/rlhf_trainers/gkd_trainer.py.
No description provided.