You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2025. It is now read-only.
akumuli (0.8.80) seems to have a memory leak somewhere in its data retrieval code.
Its total VM size on my system, after reload, is 300 MBytes. After triggering Grafana (which reads a heap of data from last week, nothing fancy) it's 615. Fair enough. However, after reloading the exact same page, which presumably repeats the exact same query, it's 685 MBytes. Another reload takes it to 726, and the reload after that is gets it to 795.
Please fix.
Update: I initially saw this with 0.8.77, but upgrading to .80 didn't change anything.
Well, it's the same query (or set of queries) every time and the system eventually runs out of memory when I do this, so no, this is memory directly allocated by akumulid.
My graph targets are simple and mostly look like this:
Activity
Lazin commentedon Sep 24, 2020
I'll take a look. Might be system cache behavior. It might prefetch part of the data volume into memory. BTW, what query are you using in Grafana?
m-u-xyz commentedon Sep 25, 2020
Well, it's the same query (or set of queries) every time and the system eventually runs out of memory when I do this, so no, this is memory directly allocated by akumulid.
My graph targets are simple and mostly look like this: