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

Cpu #4

Open
CJHFUTURE opened this issue May 26, 2017 · 5 comments
Open

Cpu #4

CJHFUTURE opened this issue May 26, 2017 · 5 comments

Comments

@CJHFUTURE
Copy link

Is it possibly o run in CPU model only?

@rozentill rozentill reopened this May 26, 2017
@rozentill
Copy link
Member

Unfortunately our project does not support for CPU, but it's possible to rewrite it for CPU use.

@CJHFUTURE
Copy link
Author

Ah, are there any plans to implement CPU? How much slower would it be to process?

@rozentill
Copy link
Member

We implemented a CPU version very early, but it was 8x slower than GPU version.

@pauldelmusica
Copy link

It might be good to have a CPU version for testing purposes, 8x slower is fine.

@lxj616
Copy link

lxj616 commented Jan 6, 2018

@rozentill @Sugarbank
I had encountered the same problem in another project (A tensorflow gpu repo), by changing the 'CUDAtensor' to 'FloatTensor' do the trick for me, although the vgg model still need to be loaded into gpu, and therefore you still need a gpu working at least, I can use cpu to enlarge the scale(pic resolution) by system memory, It's much slower, but working

I just found this fascinating repo, guess I could try something magical at February
but maybe cpu MAJOR, not cpu ONLY

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