I’ve seen this happen before. QVRPro uses a bit of CPU. More than the usage is the Load numbers. Open an SSH sedation and run the command: top
There’s a set of numbers call load average at the top. See if it is at 10 or below. If so you are fine. If it’s high then I would open a support ticket.
Hi @soljarag although you did not mention which version of the QVR Pro, I assume it is the latest version 2.7.1
We have confirmed that QVR Pro 2.7.1 has 2 scenarios that may cause increased Mongo usage:
A new installation of QVR Pro 2.7.1 may occasionally fail to create the index properly which will lead to higher Mongo usage.
QVR Pro 2.7.1 added a new Recoding Viewer which will increase Mongo usage when it create Index.
Here is the new version QVR 2.7.2 which is currently under testing and is scheduled to be release next week. It should effectively reduce Mongo usage, please give it a try.
This update fixed the first issue where the Index may fail to create, and it also added a toggle for the Recording Viewer inside Recording Storage. Disabling it should help reduce Mongo usage.