fast vector operation for pillar scatter#1676
Open
dmund95 wants to merge 1 commit intoopen-mmlab:masterfrom
Open
fast vector operation for pillar scatter#1676dmund95 wants to merge 1 commit intoopen-mmlab:masterfrom
dmund95 wants to merge 1 commit intoopen-mmlab:masterfrom
Conversation
|
@dmund95 the pipeline stayed the same and training is working for your properly? Seems like an useful improvement. |
Author
Yes, I have been training and deploying models with this change and no issues. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces fast vector operations for pillar scatter module. The for loop in exisiting module make model forward very slow. Especially with larger batch sizes.
The code has been tested to check for equal outputs before and after the changes and included in this PR
latency experiments:
Before -> Average per iteration training time ~2.9sec
After -> Average per iteration training time ~1.9sec
The training time per iteration reduces by 35% with this PR (for my set of parameters / dataset)