-
Notifications
You must be signed in to change notification settings - Fork 8
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
problems unloading the model #28
Comments
- fix issue where the goroutine will continue even though the child process is no longer running and the Process' state is not Ready - fix issue where some logs were going to stdout instead of p.logMonitor causing them to not show up in the /logs
I was able to able to reproduce the missing logs and the repeated logs. Thanks for reporting it. Can you try out the |
Awesome! now the unloading seems to work like before. Noticed the remote logs can get garbled output in the browser while the model is loading, but it will fix itself with F5 when the model has finished loading. It looked like this before reload:
Same thing was in the previous txt files if you look at those kv XX numbers they dont show up in order. But this might be issue with the server cpu load while the models are loaded? Thanks for the quick fix! |
Stop Process TTL goroutine when process is not ready (#28) - fix issue where the goroutine will continue even though the child process is no longer running and the Process' state is not Ready - fix issue where some logs were going to stdout instead of p.logMonitor causing them to not show up in the /logs - add units to unloading model message
Alright chased down that last logging bug. Things looks good on my end. I pushed a new release v76 which should be ready soon. All changes are in the main branch now. If it's not fixed for you please reopen the issue. |
Hi,
I noticed after the latest changes there seems to be issue unloading the models when ttl is reached. I set short ttl of 10seconds and tested it and this is what i see:
Above is from the process stdout. If i monitor the logs remotely with browser there is no line
!!! process for qwen-coder-32b-q4-draft stopped with error > signal: terminated
The model was actually unloaded this time but the above output is repeated approximately 1 line per second indefinetly. I saw a situation where the model was not unloaded and the line was repeated like before, but dont have any more info on that at the moment.
Version im using is:
version: local_d6ca535 (d6ca535), built at 2024-12-16T12:45:54Z
Also there seems to be some differences between the output of stdout and remote log monitoring. I will attach web.txt and stdout.txt files so you can diff them if you want. The above can be seen in them.
stdout.txt
web.txt
This is my config:
The text was updated successfully, but these errors were encountered: