-
Notifications
You must be signed in to change notification settings - Fork 195
Ramalama sits idle for several minutes #1443
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
Comments
It happens when the |
Interested in opening a PR? |
Sure I can try to put something together. |
I am now thinking this is not something we can or need to fix in RamaLama, since your system is badly configured. We can not work around all of the issues that this bad network would cause, and users expectations of ramalama to only use IPV4 if configured will not work, since container engines and the actual code within the containers will not necessarily follow the rules. |
That's fair point, there are ways how to avoid this issue on the host. |
Issue Description
Running
ramalama --debug run deepseek-coder-v2:236b
will sit idle (0% cpu being used by the process) without any output for up to 40 minutes. Then it starts the model download, which can get stuck at 99% for another several minutes.It might be something machine specific.
Steps to reproduce the issue
ramalama --debug run deepseek-coder-v2:236b
Describe the results you received
Very long waiting time for the actual download to happen.
Describe the results you expected
The download to start right away.
ramalama info output
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: