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
Installation on Windows 10 (Deepspeed inference) #2588
Comments
Hi @Eichhof, Can you please confirm if you are running this in administrative mode? Thanks, |
Thank you very much. In administrator mode I could now build the wheel. I then installed the wheel using pip. The problem now is that when calling FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\myUsername\Anaconda3\envs\huggingface\lib\site-packages\deepspeed\ops\csrc/transformer/inference/csrc/pt_binding.cpp' In fact, no folder If I set
|
Any help on this? I could not find a solution. |
Same problem |
Was somebody able to get Deepseed running for inference on Windows 10? |
(Note: these steps are for the interference only mode)
To install the generated .whl, just use: Extra Notes: About the replacement of file pt_binding.cpp: all I did was change lines 531, 532, 539, and 540: New lines 539 and 540: For anyone that just want the final .whl to install using python, here it is (no prayers needed): |
aslo report "LINK : fatal error LNK1181: cannot open input file 'aio.lib'" |
Did you use build_win.bat to build so that DS_BUILD_AIO is set to 0? |
These sentences have at least four errors- Not "Context::Instance()", but "InferenceContext::Instance()" and still can't compile, because must use <> after static_cast: The correct four lines to compile without a problem are: |
Hello
I'm running Windows 10 and I would like to install DeepSpeed to speed up inference of GPT-J. My system is the following:
When running the following command in Powershell to build the wheel
I'm getting the following error (same when running pip install deepspeed):
Can somebody help me getting inference with DeepSpeed running on Windows?
The text was updated successfully, but these errors were encountered: