Forum for questions and support relating to 1.35.x development only.
iconnor wrote: ↑Thu Mar 25, 2021 5:13 pmPossible? Yes.
You didn't say whether you are doing passthrough or encode. Encoding takes a ton of ram too (default settings will buffer 20 frames in the encoder).
Passthrough can buffer some stuff but it is encoded data and should just be ref counted so shouldn't amount to much.
--I'm using passthough. I tried to keep it as simple as possible... though sometimes it gets a little fickle. I left most of the settings close to default minus some tweaks from the upgrade (buffer from 20->2, logging, api settings etc)
dmidthun wrote: ↑Wed Mar 24, 2021 6:20 pmI'm noticing that the memory issue is only happening when the cameras are set to record of any kind, and then drops back off when the event(s) are complete and the process starts over again (~10 mins) . I also noticed that there are 4 zmc processes per camera enabled. Could this also be attributing to the resource hogging? I have my install running with 24G of ram, 12G of swap and can literally watch the usage increase even though there is little to no change in the image being captured (an empty room in my house that gets no foot traffic -- ever). 10 rtsp cameras set to monitor == 4.5~5.5G RAM; change 1 to Mocord, system will again start hoarding memory.
Isaac, is there possibly a memory leak in the zmc process when in record mode?
ZM 1.35/master (latest)
8 Merkury 720p 'smartcams; hacked'
Ovirt 4.4.4 KVM Env - 2CPU, 24G RAM, 72G vdrive; 60sda 12sdb(swap) - Nimble backend storage @ 10G FC
Who is online
Users browsing this forum: No registered users and 3 guests