WSL: Training on CPU even when having compatible NVIDIA GPU
See original GitHub issueIssue description
Ivadomed doing training on cpu even though i have a compatible nvidia gpu and installed via requirements_gpu.txt
Current behavior
Training on cpu
Expected behavior
Training on gpu
Steps to reproduce
All steps in https://ivadomed.org/en/latest/installation.html with approach 2
Environment
Windows 10 Pro : (WSL1 Ubuntu 20.04 with python 3.7) and (WSL2 Ubuntu 18.04 with python 3.8) Nvidia Geforce gtx 1050
Solutions tried
Tried https://docs.nvidia.com/cuda/wsl-user-guide/index.html, but the current insider preview build (which is a version of Windows 11) is not stable (crashing at every startup), had to do a clean installation of Windows 10 afterwards.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Leveling up CUDA Performance on WSL2 with New ...
This technical blog post In this post focuses on the current state of the CUDA performance on WSL2, the various performance-centric ...
Read more >Enabling GPU acceleration on Ubuntu on WSL2 with the ...
Enabling GPU acceleration on Ubuntu on WSL2 with the NVIDIA CUDA Platform · 1. Overview · 2. Install the appropriate Windows vGPU driver...
Read more >GPU acceleration in WSL - FAQ - Microsoft Learn
How do I enable DirectML acceleration? The DirectML device is enabled by default, assuming you have an appropriate DirectX 12 GPU available. TensorFlow ......
Read more >GPU accelerated ML training inside the Windows Subsystem ...
Adding GPU compute support to WSL has been our #1 most requested feature since the first release. Over the last few years, the...
Read more >GPU Accelerated Machine Learning with WSL 2 - YouTube
Adding GPU compute support to Windows Subsystem for Linux ( WSL ) has been the #1 most requested feature since the first WSL...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yup. Will update this ASAP. Windows Torch CPU based IvadoMed has been running and well tested through GitHub Action CI processes for a long time post PR #757 but the Windows GPU based approaches has not undergone the same systematic tests. Going to test it out shortly before the documentation update.
@dyt811 if windows is supported natively, this is something we need to fix in the doc