-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
Type instabilities lead to insane number of CPU allocations on grouped convolutions #520
Labels
Comments
Closing no issue when on GPU
|
ToucheSir
changed the title
Depthwise convolutions lead to insane number of CPU allocations or GPU version broken
Type instabilities lead to insane number of CPU allocations on grouped convolutions
Jul 5, 2023
Since the MWE has a lot of useful information, I'm taking the liberty of reopening this with a different focus. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is the MWE
Result of above is run twice
Expected result ~70 CPU allocations, not 128400 CPU allocations, in a deeper network it puts considerable pressure on GC and kills performance.
I tried
depthwiseconv
in my code but it has another problem that it's not GPU friendly.So it's either making depathwiseconv GPU friendly or fixing insane allocations of
conv
.The text was updated successfully, but these errors were encountered: