-
Notifications
You must be signed in to change notification settings - Fork 113
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
Memory Issues #93
Comments
I have the same problem with my Jetson Nano / GTX 1650 I have maxed out at 3869MB so far on the GTX. So between teaching people I have to restart the container. |
is there any update on this? |
Just wondering if there has been any progress on the memory issue / memory leak where it doesn't release memory after training in faces? |
I think I'm having the same on the Windows/GPU version. I can't tell how much memory is being used per process, either due to a limitation of nvidia-smi on Windows, my card (P400) or some combination. However, there is a definite correlation between GPU memory, and DeepStack entering an unrecoverable (without a restart) state where all requests result in a 100/Timeout error. Without better logs (#142) I can't be sure where exactly what is going on, but there's a strong correlation. I've been tracking troubleshooting and the steps I've taken here: https://ipcamtalk.com/threads/deepstack-gpu-memory-issue-error-100-timeout-after-several-hours.60827/ |
I trained 4 face images and it's using more than half of the memory on jetson nano. If I train two more images it runs out of memory. |
System Specs:
Deepstack process does not release memory after processing.
Memory usage upon starting Deepstack in docker (927mb)
memory @ 3.2 GB after registering 27 faces
This high memory blockage prevents me from performing other functions including registering faces
Either I'm missing something or memory management need some serious improvement. The only way around this is to keep on stopping the docker container after each action
Thoughts?
The text was updated successfully, but these errors were encountered: