-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
The demo (ZF) with cuDNN is a little slower than without cuDNN? #114
Comments
There is no guarantee that cuDNN will always be faster. The runtime depends on the network structure, your GPU model, the cuDNN version and how you choose to compute convolution within cuDNN. For example, cuDNN is considerably slower on VGG16 than Caffe's native implementation before V4. |
Oh, I see! It is my mistake to think the cuDNN will always be faster. Thanks for your answer, it is really helpful for us. |
Well, this is tricky question. The major advantage of cuDNN over Caffe's native implementation part is the convolution part. I was checking the code in Caffe and realized that Caffe is not using the full power of cuDNN. For convolution, cuDNN offers different algorithms with an auto-tune function that selects the best one. In Caffe, this auto-tune feature is "off" due to a management issue. You can also check the discussion here. |
Alright, that looks really complex. But it is not necessary for studies. |
@JohnnyY8 how can you disable using cudnn? |
I have gotten the commit: 96dc9f1 according to #108 . But the cuDNN still slow the demo down.
Anyone can help me? Thank you!
The text was updated successfully, but these errors were encountered: