-
Notifications
You must be signed in to change notification settings - Fork 123
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
high memory usage #546
Comments
Thanks for reporting the issue. Let's try to fix this. |
Thank you. I have started a second instance with example cronjobs. If RAM usage goes up too after some days, I'll share this example. |
My test instance starts at about 10 MB RAM and now need 60 MB RAM. In 3 days. Command:
Using 4 dags from your example:
My other instance now runs for 12 days and need 122 MB RAM. Btw, running of course your latest v1.12.11 release. Thank you. |
Thanks a lot! Will try to pprof using these examples. |
Can you reproduce the memory leak? |
Sorry, not yet because of my bandwidth, but I have removed some unnecessary heap allocations to fix other problems. So it might solve the problem to some extent. |
Ok, will try it after a new release. |
Btw, would you mind clarify the context where you're running Dagu? :) I'm wondering what makes the memory usage so important on your environment. |
Some Raspberry Pi provides only 1GB of RAM or even less (512MB!). It makes you sensible for RAM usage. Any swapping means higher wearing of the SD card and you really don't like a system that is crashed for this reason. But regardless of this, I think any memory leak is something that should be fixed: |
I see, thanks for your clarification. |
I run dagu with a single instance for about 9 days. Still testing dagu with 3 cronjobs that runs every few minutes. RAM usage starts at around 15MB. After 9 days it use 92MB RAM. In the past it even use over 300MB RAM with a longer uptime.
The text was updated successfully, but these errors were encountered: