-
Notifications
You must be signed in to change notification settings - Fork 813
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
Running install.sh after git clone requires over 200GB Ram #732
Comments
The ram spike happaned in this stage before collecting numpy and other packages.
|
Thanks for reporting this issue! We will update the |
there seemed to be some confusion. I faced two issues.
no matter you have limited ram or not.
|
Thanks for sharing more information! Let us update the document and dependency to reflect the change. Meanwhile, it can also be relevant to system versions and the local environment. Previously we have installed lmflow in Google Colab (with RAM 80G), which does not seem to have issues. It would be greatly appreciated if you could share more information about the 128 GB system, and if possible, test if a similar problem occurs with other |
Hello, excuse me, when I use the “bash install.sh" command with 96GB RAM, the server is stuck, why? |
Thanks for your interest in LMFlow! It is possible that some dependency installation requires local compilation, which may consume a lot of memory. To check which package stuck the process, you may run |
I have a server with 128GB ram and it will be freeze when I follow the quick start procedure. On another server with 512GB ram it's fine. I think adding this warning in read.me could be helpful for other with limited ram.
Also, when I follow along the quick start procedure. I noticed I need to do
manually before install.sh can be successfully run.
The text was updated successfully, but these errors were encountered: