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

about cudnn #13

Closed
duanLH opened this issue Oct 13, 2016 · 3 comments
Closed

about cudnn #13

duanLH opened this issue Oct 13, 2016 · 3 comments
Assignees

Comments

@duanLH
Copy link

duanLH commented Oct 13, 2016

you said "Do NOT uncomment USE_CUDNN := 1 (for running PVANET, cuDNN is slower than Caffe native implementation)", I want to know, the slower is include training and test? I train my net without cudnn, its so slow

@sanghoon
Copy link
Owner

I'm sorry we made a confusion here.
It's totally okay to uncomment USE_CUDNN if it makes your training faster.
It just means that commenting 'USE_CUDNN' worked faster in our computational environments.

I'll update README.

FYI, for our published results,
training of a network took 7~14 days with Titan X or GTX1080.

@happyharrycn
Copy link

I think it is possible to also make testing faster with cuDNN, although I have not got a chance to test it on PVANET. The performance issue is that cuDNN had bad implementations for certain convolutions (e.g. 1x1 convolutions with stride=1, which is used a couple of times in PVANET). You can still compile Caffe with cuDNN and put engine: CAFFE under convolution_param in these layers.

@sanghoon sanghoon self-assigned this Oct 21, 2016
@jay2002
Copy link

jay2002 commented Oct 23, 2016

@happyharrycn cool solution!
I have tried it and it really does work

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

4 participants