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
Some things wrong when building the CPU-only version. #2
Comments
I remember running in to some cl.exe errors initially, but I can't remember what I did to fix them. Let me know if you figure it out! |
oh, I see. I will try to fix it. But can you send me the the wheel file to my mailbox(my version of tensorflow is same to you). I can't wait to try how fast it can be than before, it is my email: ytdengliang@gmail.com |
I wish it was as easy as just giving you the wheel file! Unfortunately, TensorFlow HAS to be built on your machine for the TOCO tools to work. There's something extra about the build process that doesn't happen during a normal wheel file installation. I'll have to ask a software developer why it has to be built on the PC rather than just installed. |
Hey, I think I have found a solution, but now I have to sleep first. I will give the solution in tomorrow morning. |
Hey, at the end of the fight against various bugs, I successfully ran the TF Lite model. This is really a great tutorial. But before I sorted out this series of errors, I found that it run in my laptop have only 1.96FPS, it seem don't use the GPU i have in laptop, what should i do? |
|
Yeah!! I'm glad you got it working. Can you tell me how you resolved the error related to cl.exe? It runs very slow on my gaming PC too. The TFLite runtime does NOT use the GPU, so it runs slower than regular TensorFlow does if you have GPU on your PC. The benefit comes when you don't have a GPU: then TFLite runs much faster than regular TensorFlow! Unfortunately, this means that if you were just hoping to use TFLite to speed up FPS on your laptop, then you'll have to try something else. You could try installing Ubuntu on a separate partition on your laptop, and then using it with the Coral USB Accelerator. (It won't work with Windows.) You'll be able to use the same instructions as I wrote for using the Accelerator on the Raspberry Pi (which I'm still working on). Sorry there isn't an easier way to speed up FPS! |
hey, let start it. When I got these problems, I started to check all of these steps before build. And I found that may be due to insufficient memory(my RAM only 8G) and insufficient storage(it use 17.8G in my
you should use --local_resources 2048,.5,1.0 instead of --local_ram_resources=2048, I think it not use in the bazel which version is 0.21.0.
And it can build with no problem!!!(But it will last a long time, in my case, it last 3 hours to build) |
Closing due to inactivity. |
hey, I got some things wrong when I try to build the CPU-only version.
the configuration session look like this
Then it runs very well at first,but it encountered some errors in the middle,just like this:
and this:
I don't know if this error message is sufficient, if you need more details,just ask me.
The text was updated successfully, but these errors were encountered: