-
Notifications
You must be signed in to change notification settings - Fork 74.1k
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
What is preventing TF to use GPU when used in native windows? #69750
Comments
@eabase according to Simon_Au-Yong in a relative discussion on the TensorFlow Forum:
|
As you can see from the above comment, the only obstacle is the "Desire". Besides, their target audience doesn't seem to be Windows users (let alone home users who need to install this package because it's a requirement for something else). |
Up to 2022, I was in the team responsible for making TF work on all platforms. Windows, and especially GPU, was the one with the most breakages and also the one with the least expertise. Everyone was focused on Linux and only a team of ~3 was working on the other ecosystems. Since then, none of those is still in TF and support is very reduced, even for Linux |
@mihaimaruseac I am relatively a newbie in the world of TensorFlow but I wonder why valuable TensorFlow team members left the team and why in general the number of members was so radically reduced. I really don't get it.. |
Hi Guys! @sgkouzias @thiagojramos @mihaimaruseac
Then we have the |
It looks like the issue is assigned to @Venkat6871 . @Venkat6871 could you provide some useful guidance? |
Professor Alvaro Rodriguez writes in a relevant discussion on the TensorFlow Forum:
|
Reorg during pandemic, shift of priorities, old manager and tech lead left, almost no-one who worked on TF pre-2.0 was still left in the team, JAX, Goodhart's law (in multiple instances).
JAX is what is the future now from Google. Or PyTorch. If you can use Keras 3 (which is not the default within TF -- or it should not be), you should be backend agnostic, but there's still a lot of work left to do to cover everything. |
Unfortunately, most files that were there to support compiling on GPU on Windows are no longer in the repo, so there's not really a simple path forward. |
@mihaimaruseac thank you so much for the insightful response. I am really grateful and do appreciate your efforts and generally the TensorFlow & Keras team (those who left the team and those who crafted and maintain the new, more inclusive and powerful Keras). I am a fan of the "progressive disclosure of complexity" core principle of Keras. If JAX is the future I will embrace it. |
I guess what I am saying, that the c/c++ used in the linux (WSL) compilation, should be straight forward to adjust to compile in native windows, unless they try to use native .NET/C#/Windows API calls. Forget all the stupid setup/build scripts, they only confuse everyone. This, of course, as long as there are no hard-coded libraries or other Anyway, thank you so much for providing the summary and clarity of the situation. Is anyone aware of some summary or methodology of translating legacy TF code into Torch or Keras? |
This is the main issue. The Bazel files and macros that allowed compiling on GPU on Windows were excised. The macros assume in many places that they only build Then, there's an issue that the old build scripts used MSVC + nvcc for CUDA compilation, but now everything is on clang, so the path on Windows + CUDA has not been tested at all. |
Linking, relevant: #59918 |
@mihaimaruseac I can try to see if I can reproduce that build under MSYS. (I don't see why it couldn't be done.) |
I think running https://www.tensorflow.org/install/source under WSL should work |
We keep getting told, repeatedly that TF no longer "supports" using GPU on versions
>2.10
. However, the reason why this is so, is nowhere to be found.Can someone from the TF community please explain what is the problem with TF having GPU support for native windows environment?
Finally, since the wording is "supported" (and it was supported before), how can we go about implementing this support on our own?
What are the python package requirements, and native windows C/C++/C# compiler requirements?
The text was updated successfully, but these errors were encountered: