8 ms·
To be honest I don't quite understand what stopped those developers from running machine learning on their GPUs under Windows itself. Most frameworks work just
by lostmsu 6y ago
To be honest I don't quite understand what stopped those developers from running machine learning on their GPUs under Windows itself. Most frameworks work just fine. I've been doing quite a lot of TensorFlow with both Python and .NET.
The only time I faced the need for Linux box is trying a demo project from OpenAI, which did not use the features it required Linux for on a single machine anyway.
- rezonant 6y agoI believe the purpose is for devs who are deploying to Linux, their toolchain may not fully work in Windows, but they want to have a similar dev/test env within Windows... pretty much the whole point of Windows Subsystem for Linux (WSL). It's not that the frameworks don't work on Windows, it's the deployment tech, like Docker, Ansible, their build scripts etc etc. Some users may be doing something totally custom on top of the GPU without a framework layer but that is probably very few users. I'd have to guess though that those users would be the type of users that would get MS to go through the effort though...
- lostmsu 6y agoDo people actually use Docker and Ansible a lot for ML??? Doing something custom on top of the GPU is also not much different on Windows, than Linux. CUDA is basically the same. OpenCL and Vulkan are available too. I'd like to hear perspective of a person, who actually does ML specifically on Linux for some reason.
- hetspookjee 6y agoWell CUDA is only one thing. Especially in the python environment it's only a matter for time before you run in some wierd dependency issue that is Windows only. For example, getting XGBoost completely up and running on Windows requires you to either build it yourself or download a .dll from a university link. Installing it on Linux is just a proper pip install. Also windows not having a build in C compiler makes you dependent on the horribly convoluted Visual Basic stack that seems to have a lot of dependencies for some python ML libraries. Docker makes it a lot better to run and I almost always deploy in a docker container because the ML modules I deliver are often interacted with as a black box with a REST API on top.
- lostmsu 6y agoIt looks like Anaconda supports XGBoost on Windows. You might be right about C compiler. But something itched when you mentioned Docker. Could getting Windows SDK installed be harder, than installing Docker?
- rezonant 6y agoI just use chocolatey for that > choco install windows-sdk-10.0 That being said I had to avoid installing VS 2019 for quite awhile because Node.js native module build chain couldn't work with it. There are complexities
- NOGDP 6y agoI do all of my development on linux, if I can, but to be honest the GPU support is generally better on windows because that seems to be the main platform AMD and NVIDIA target - though linux support is not too bad. GPU support is the only potential benefit in using windows that I can think of though. Everything from package management, to build tools, FOSS support, community, troubleshooting, etc. is generally better on linux.
- numpad0 6y agoDocker at this point is InstallShield infrastructure for startup production quality freewares
- visarga 6y agoIt is being used both for training and inference in order to package dependencies and scale up.
- lostmsu 6y agoJust curious: what kind of models are you training, that require scale-up using Docker/Ansible/Kubernetes?
- cma 6y agoThings like filename limits and command length limits seem to get hit on windows way more frequently, making all code more fragile in general, and a million other little things. Even popular libraries like zeromq don't support namedpipes on windows because of how complicated they are and how different to everywhere else. Just determining what visual studio version is installed seems to trip up projects all the time.
- bjoernbu 6y agoMostly doing several kinds of NLP: My actual setup is a Windows Laptop to SSH into Linux machines w/ tmux session. However, I really appreciate WSL for working offline, etc. My main reason: It is the most convenient way to have Unix tools (grep/sort/cut/sed/less/...) and bash available. Cygwin always was a pain, MinGW / GitBash felt much better, but ultimately WSL just feels best. These tools are incredibly valuable to my workflow. Sure, stuff like pandas can be nice for small datasets, and some data sits in some DB/Kafka/distributed system. But there have been countless cases where unix tools allowed me to take xxGB zpfiles of text and do basic examination or even build baseline models within a few hours. Sure, there always are alternatives to use these tools and there are many equivalents. But I would always prefer WSL + conda for Linux to a typical "Windows Conda" installation with that weird GUI and the need to install so many different applications to even just look into the first or last few lines of a huge textfile. EDIT: That said, of course I can/could always just run a juypter notebook under windows using windows cuda + GPU and share files with a WSL bash where I do my modifications. But again, everything within the same systems just feels better (ipython shell magic, no worries about if paths to the same file are really identical, etc) and while this is by no means a game-changer, it is just nicer that way.
- andyljones 6y agoThe reason to use Linux is to follow the crowd. I use Nvidia's docker container because the plurality of devs use it. Over the course of my career I've found that well-trodden paths tend to have a _lot_ fewer bugs thanks to other people finding them first, and when I do get some https://github.com/pytorch/pytorch/issues/37790 https://github.com/pytorch/pytorch/issues/37790 weird https://github.com/pytorch/pytorch/issues/32575 https://github.com/pytorch/pytorch/issues/32575 bug https://github.com/pytorch/pytorch/issues/25301 https://github.com/pytorch/pytorch/issues/25301 I don't have to spend time explaining or justifying or isolating my setup. Conversely though, my work is itself off the beaten path enough that I'm likely to run into weird bugs. If I was pushing images through a CNN, that'd be well-trodden enough on every platform that I'd be a lot less fussed about which particular platform I use.
- teleforce 6y agoThis mainly to woo developers who are now working on Mac OS or thinking to use Mac OS to use Windows and WSL combination instead for ML & AI application development.
- hetspookjee 6y agoMy experience with GPU accelerated development is quite horrible on Windows for anything other than the NVIDIA prepped docker container. There was always something missing or some drover was incompatible. In the long run I have always regretted developping Python on Windows, also often because whatever was developped was to be deployed on a Linux box. I do not think it's purely windows to blame here though. It's only quite recently that NVIDIA started fixing their documentation and instructions on getting all the right CUDA CuDNN stuff running properly on a system.
- bitcrazed 6y agoHi. PM on Windows & WSL here. Imagine if you could run AI/ML apps and tools that are coded to take advantage of DirectML on Windows and/or atop DirectML via WSL. Now you can run the tools you want and need in whichever environment you like ... on any (capable) GPU you like: You don't have to buy a particular vendor's GPU to run your code. If you're old like me and remember the dark ol' days when games shipped with specific drivers for (early) GPU cards/chips, but failed to run at all if you didn't have one of the supported cards, you'll understand why this is a big deal.
- NOGDP 6y ago> If you're old like me and remember the dark ol' days when games shipped with specific drivers for (early) GPU cards/chips, but failed to run at all if you didn't have one of the supported cards, you'll understand why this is a big deal. Maybe I'm not that old, but I'm old enough to remember the days when microsoft was intentionally degrading opengl performance on windows ;).
- visarga 6y agoProb. different PM though.
- 1bc29b36f623ba8 6y agoThis. Some games would have a handful of different renderers for different setups, while other games would only support one specific card type (and if you were lucky, a software renderer). Those days sucked. Bigtime. If we can avoid doing the same mistakes for machine learning then we should.
- anonymoushn 6y agoI couldn't get torch's cuda stuff working on windows. Runs fine on OSX though.
- hcarlens 6y agoLots of ML frameworks are built for Linux/UNIX first. The OpenAI projects you mentioned are a good example, but also projects like Ray (ray.io). Even PyTorch - a lot of stuff works fine, but their parallel DataLoaders actually work slower on Windows than the single-threaded ones (see this github issue: https://github.com/pytorch/pytorch/issues/12831 https://github.com/pytorch/pytorch/issues/12831 )
- mcv 6y agoBut Windows is a painful OS to use for anything other than gaming. Ideally, I'd like to see the exact opposite of this: run Linux with a Windows subsystem just for gaming.
- albertzeyer 6y agoThat's exactly what Wine is.
- mcv 6y agoIt's exactly what Wine wants to be. Sadly that's not quite the same thing.
- boudin 6y agoWhat do you mean? Wine has a different architecture because distributing microsoft binaries is not legal, so technically it's not the same thing, but it still does an amazing job and a lot of apps/games works flawlessly.
- mcv 6y agoIt does an amazing job, but a lot of apps and games do not work flawlessly. Or didn't, last time I tried Wine. Maybe this situation has changed a lot since then, which would be awesome.
- dependenttypes 6y agoEvery single versions has a lot of improvements, esp regarding compatibility. I suggest giving it a try once again.
- zokier 6y agoThat directly implies that every single version has had lot to improve. And this is not to diss wine, but it is difficult problem they are tackling.
- munchbunny 6y agoIf your dev or production stack is Linux based, I think it makes sense to try to bring the GPU to your dev stack instead of the other way around. If you're working with other devs who are on actual Linux stacks, it'd be a pain in the ass to always require for there to be hybrid Windows/Linux tooling.