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.

Sign up for GitHub

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

Jump to bottom

Is cutorch.synchronize() necessary? #15

Open
ffmpbgrnn opened this issue Sep 4, 2015 · 2 comments
Open

Is cutorch.synchronize() necessary? #15

ffmpbgrnn opened this issue Sep 4, 2015 · 2 comments

Comments

@ffmpbgrnn
Copy link

Hi, I found cutorch.synchronize() was used in main.lua#L184. Isn't backward() blocking? And in my experiment, cutorch.synchronize() will cost much time.
@wojzaremba
Copy link
Owner

It was necessary a year ago when I was writing it. Without it code was crashing.

I am not sure if it is necessary now. Torch used to be not the most stable environment.

@ffmpbgrnn
Copy link
Author

Thank you! @soumith, do you have idea about this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wojzaremba @ffmpbgrnn