Closed AymenTlili131 closed 1 year ago
Hello @AymenTlili131,
We really appreciate your feedback. I was able to reproduce the same error on my end and it seems to me that this is not a matter of NCCL setup but the numbers of GPUs you're trying to assign. When running on NCCL, torch distributed receives the argument --nproc_per_node
as the number of GPUs you have available in your sytem to run the simulation, however FLUTE requires at least 2 in order to launch: 1 Server and 1 Worker that can execute many clients, but I can see you only have 1 available (GPU 0).
This is the stacktrace .. as you can see the problem occurs at the assignation time.
I took a look at NCCL test repo and noticed that the -g
argument correspond to the number of available GPUs, this is the reason of the fail, given that you only have 1 available it's not able to run with a higher number.
You can find more information about FLUTE architecture here. There is one issue already open for this situation here: https://github.com/microsoft/msrflute/issues/15 , we apologize for the inconvenience at this moment.
Regarding the comments about the requirements/ python versions, we will make sure to update them during the next commit.
Let me know if this information is useful or if we can provide more support on this. 🙂
Thanks, Mirian
Thanks for writing back so soon , I'll request access to a workstation with 2 or more GPUs and test it for myself but this is a solid and good explination to why the error was raised , thanks ! I'd still like to keep the issue open until I confirm that it indeed works (not more than a week ). Reading the linked FLUTE architecture it should and will work but hopefully i won't take long with the environment setup and testing before I get back to you .
Thanks @AymenTlili131! Let us know if this issue persists.
Regards, Mirian.
Hey @Mirian-Hipolito Things are up and running on my end . I'm grateful for your explanation and support and hope you and the maintainers have a wonderful rest of week . I'll make sure to cite the FLUTE team if I find anything useful ! thanks again Kind regards
Hello @AymenTlili131, we are happy to share that we have removed the restriction of minimum number of GPUs to run FLUTE in our latest release. For more documentation about how to run an experiments using a single GPU, please refer to the README.
Hey Mirian , This is great news .I gained access to other GPUs meanwhile and did experiment with working on them remotely but thanks to your efforts and your colleagues' I can experiment with tweaks and proofs of ideas at a much smaller scale . Greatly appreciate and thanks to the entire Microsoft family
HI there maintainers, first off I'm thankful to the devs and engineering that went behind setting up this framework .I tried picking it up and as a to simulating GPU parallel computing with NCCL I ran into some issues . here's the error i'm currently trying to fix .
error [1]
My system is ZorinOS 16 which is based on ubuntu20.04 , I'm trying to use an Nvidia RTX 3060 GPU
nvidia-smi returns the following
and nvcc --version returns the following
this screenshot displays that I have pytorch environment almost ready to go .
now when trying to install nccl , I can't find a way to confirm if the installation is succesful , or where the nccl home is .
using the command (
python -m torch.distributed.run --nproc_per_node=3 e2e_trainer.py -dataPath ./testing -outputPath scratch -config testing/hello_world_nlg_gru.yaml -task nlg_gru -backend nccl
) in readme yields the following and no models being stored in the scratch folders error [1]'s original stackand before that I tried running pytest -v -s in ./testing
so my guess was that I haven't setup NCCL properly , I tried to find the legacy build compatible with mine from https://developer.nvidia.com/nccl/nccl-legacy-downloads and got NCCL 2.11.4, for CUDA 11.4, September 7, 2021
and as instructed used " sudo apt install libnccl2=2.11.4-1+cuda11.4 libnccl-dev=2.11.4-1+cuda11.4 " as instructed which went smoothly but I still encountered the older stack trace .
going to nvidia's NCCL test repo , I skip the installation steps because I have an official release then try to do "make" then "./build/all_reduce_perf -b 8 -e 256M -f 2 -g 1" (I tried changed the -g argument to 4 or keeping ngpus) and got the same error either way
./build/all_reduce_perf: symbol lookup error: ./build/all_reduce_perf: undefined symbol: ncclRedOpCreatePreMulSum
now that's where I stopped with those 2 issues where I feel solving one would help the other .
but before I got this far I had to reformat the workstation acouple times seeing Nvidia fails to keep all the necessary compatibility information in one place but this post saved me in my previous environments , I managed to get FLute running on gloo but I still had a similer warning stack trace but models could be saved .
in this fresh environment I also had trouble importing and using the python built-in subprocess module specifically because the "run" method generated errors that I worked around around with this https://stackoverflow.com/questions/40590192/getting-an-error-attributeerror-module-object-has-no-attribute-run-while but even then I was still receiving an error with that solution because "text" had a TypeError and couldn't be passed to Popen class constructor
Failed: TypeError: __init__() got an unexpected keyword argument 'text'
so my investigation led to the fact that the text argument was added after python 3.7 and when your readme.md suggests 3.8 thus the problem I can understand if you have been working on this project for a long time but this could have been a seperate issue because it causes the tests in pytest -v -s to fail. that you can label as an enhancement but I felt it could be related to why the processes aren't being assigned to the virtual gpus properly.
other honorable mentions include using : sickit-learn instead of deprecated sklearn in requirements.txt and that using newest version of pytorch 1.13 compatible with cuda 11.7 leaves the speech recognition task with deprecated torchaudio
Apologies if I mentioned several irrelevant steps or issues but I hope that I can get an exact answer to error[1]'s stack trace and quickly get back to focusing on the experimentation side research . thanks to the msrflute team and hope to hear from u soon