[ovirt-users] Re: Upgraded to oVirt 4.4.9, still have vdsmd memory leak
Once upon a time, Victor Stinner <vstinner(a)redhat.com> said:
I wrote the tracemalloc module which is easy to use on Python 3.4
and
newer. If you take tracemalloc snapshots while the memory usage is
growing, and comparing snapshots don't show anything obvious, you can
maybe suspect memory fragmentation. You're talking about 4 GB of
memory usage, I don't think that memory fragmentation can explain it.
Do you need my help to use tracemalloc?
Any tips on where I should add that to vdsm's code?
It'll probably take me a little time to get this going - I'm only seeing
this on my production cluster (of course), not my dev cluster. One
difference is prod is iSCSI storage with multipath, while dev is Gluster
(so that may be a clue to the source of the issue).
--
Chris Adams <cma(a)cmadams.net>