-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Docker Container is unhealthy on my Synology NAS (but appears to work) - can this be fixed? #80
Comments
Hi! Thanks for reporting this. I'll take a look and come back to you if I have any questions. |
@cleverestx There seems not to be any memory leaking as far as i have checked. This is the pwgen.joonatanh.com docker and even with approximately 200 unique users per day, there is absolutely no issues with the memory: |
Thank you for the details. I have 20GB of RAM on my NAS and to my
knowledge, I should have about 8GB free at any given time, even with other
stuff running...
I'll double check the actual usage tonight though.... I was just concerned
that it was saying it was unhealthy, and those logs...
…On Tue, Apr 9, 2024, 7:19 AM jocxfin ***@***.***> wrote:
@cleverestx <https://github.com/cleverestx> There seems not to be any
memory leaking as far as i have checked.
How much of memory is free on your system? Could it be that your system is
running our of reserved memory?
Seems like your synology should have 4gb of ram. I tried to overload the
memory by opening 100 sessions of the application without caching and it
never went over 200MB and i never saw any issues you have.
This is the pwgen.joonatanh.com docker and even with approximately 200
unique users per day, there is absolutely no issues with the memory:
image.png (view on web)
<https://github.com/jocxfin/pwgen/assets/19174728/d81d746c-6ed5-46f0-af8c-88fc0dba3599>
—
Reply to this email directly, view it on GitHub
<#80 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG4Q6JLKYV4ORLU3JYWXFALY4PTFZAVCNFSM6AAAAABF55ELUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBVGE3DGNJWGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I actually took some time and tried to research this issue. As I double checked, there should not be any memory leaking even after long time. Only thing I found, was a Synology update causing a general memory leakage, but this happened in 2021 and they fixed that with an update. But they said that if users are still having issues with memory leaks, removing the container and re-deploying it should stop that. So maybe give that a go? I also thought maybe it's due to the amount of workers present (by default 2 and 4 threads) so I'll make a dev build soon where there will be the possibility to use the envs Edit: my bad, apparently i already had made the change and it should be available in jocxfin/pwgen-dev if you want to test. Just add new envs for WORKERS=1 and THREADS=2 |
Thank you! I will check it out soon! |
Concerned about a memory leak or other issues though. How do I fix this?
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: