Hi,
i have pingwatch running for several weeks on a Raspi4 at home as well as on a VPS onthe internet.
Today i received an email from the VPS monitoring tool that warned me about high memory usage. I didn't suspect pingwatch right away because there are plenty of other applications running on the VPS. However pingwatch had - if i read htop output correctly - something over 900MB of memory allocated. And approximately this amount was gone from the memory gauge when i quit pingwatch.
Similar on the Raspi (while not so critical because it has 4GB of memory and it basically just runs a DNS server at the moment), pingwatch had something about 500-600MB allocated.
This took several weeks (4 or 5 maybe?) now.
I can think of quite easy workarounds like restarting pingwatch every night (I wanted to find out how to write systemd service units for it anyway), but maybe there is something in the go code that could be optimized to not have this happen?
Thanks
Hi,
i have pingwatch running for several weeks on a Raspi4 at home as well as on a VPS onthe internet.
Today i received an email from the VPS monitoring tool that warned me about high memory usage. I didn't suspect pingwatch right away because there are plenty of other applications running on the VPS. However pingwatch had - if i read htop output correctly - something over 900MB of memory allocated. And approximately this amount was gone from the memory gauge when i quit pingwatch.
Similar on the Raspi (while not so critical because it has 4GB of memory and it basically just runs a DNS server at the moment), pingwatch had something about 500-600MB allocated.
This took several weeks (4 or 5 maybe?) now.
I can think of quite easy workarounds like restarting pingwatch every night (I wanted to find out how to write systemd service units for it anyway), but maybe there is something in the go code that could be optimized to not have this happen?
Thanks