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

Wall-clock performance issues #2

Open
verbose-void opened this issue Nov 12, 2020 · 2 comments
Open

Wall-clock performance issues #2

verbose-void opened this issue Nov 12, 2020 · 2 comments

Comments

@verbose-void
Copy link

LambdaResNet50 in comparison to a normal ResNet50 from my testing is 7x slower. I am training on ImageNet, and I am comparing your LambdaResNet50 to a torch.hub ResNet50.

Is this to be expected?

@leaderj1001
Copy link
Owner

Perhaps the torch.einsum computation time is too slow.
I will find another way to reduce the computation time.

Thanks

@verbose-void
Copy link
Author

yeah, that was the conclusion i came to as well. it's significantly faster than torch's einops still.

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

No branches or pull requests

2 participants