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

When I try to run a python program after importing Tensorflow library I get this message #8234

Closed
prajjwal1 opened this issue Mar 9, 2017 · 2 comments
Closed

When I try to run a python program after importing Tensorflow library I get this message #8234

prajjwal1 opened this issue Mar 9, 2017 · 2 comments

Comments

@prajjwal1
Copy link

W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE3 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.1 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.2 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX2 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use FMA instructions, but these are available on your machine and could speed up CPU computations.
@AFAgarap
Copy link

AFAgarap commented Mar 9, 2017 •
edited

@prajjwalin You're using the CPU version of TensorFlow, right? If you use the GPU version, you'll have a different output message. You'll have one like this:

I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcublas.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcudnn.so.5 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcufft.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcurand.so.8.0 locally

You may ignore it, but if you want faster computation, use the GPU, and you'll have an output message like the one I posted above.

@prb12
Copy link
Member

prb12 commented Mar 9, 2017

These warnings are harmless, and can safely be ignored.

They are there as a gentle reminder to people who are benchmarking TensorFlow that it is possible to generate faster CPU code if various processor specific build options are enabled. (In generic binary builds are unable to turn on these options.)

Closing since this is not a bug/issue and really a general usage question. (which are best sent to StackOverflow for future reference!)

@prb12 prb12 closed this as completed Mar 9, 2017
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
3 participants
@AFAgarap @prb12 @prajjwal1