Increased memory use with NX v5?
Answered
I've noticed across a number of VM's (Ubuntu 20.04) we have running v5 of NX that we are getting increased memory use over time. I noticed in the changelog for build 36410 a few memory related fixes were included but after upgrading our memory use on all the servers in the hive running this build still look something like below over the period of a few weeks. I've increased the memory a fair amount above what we were running in v4.2.
-
Dear Campbell Steven,
I hope this message finds you well. I wanted to touch base with you regarding the graph you shared with me. While reviewing the graph, I did have a moment of confusion as I was anticipating a gradual increase in memory consumption leading up to a drop once the server crashed or was restarted. A bit more information is required to understand the issue you experience.
That being said, I wanted to confirm that your observation is indeed correct - the 5.0 version of the software utilizes more RAM as compared to previous versions. This is primarily due to a different authentication method. While this may have a slight impact on memory consumption, rest assured that the influence should be minimal and well within the recommended hardware specifications. Also, the avg load should remain more or less equal over time, with perhaps some spikes in case many events at the same time occur.
Please let me know if there is anything further that I can assist you with. I look forward to hearing from you soon.
Best regards.
-
Thanks for the confirmation Norman that v5 does have increased memory use. I upgraded it from 8GB to 12GB (as you can see on the graph where the line jumps up further on Mar 21) but it still seems to keep on consuming until things start going into swap and in the end I restart it which you can see in the graph. Also happy to add more RAM if we think it should stabilise on memory use at some point.
The graph shows available memory, so the downward trend is memory being allocated, until eventually our alerting kicks in and we end up restarting (the sharp lines up, e.g. around Mar 21) . I'm happy to adjust alerting thresholds etc. but from what I can tell it just continues using RAM until we start using swap which isn't ideal.
This server has 80 cameras on it.
-
Hello Campbell Steven,
Thank you for providing us with additional clarification. It has helped to shed light on the issue at hand.
We kindly request that you update to the latest public patch, which is version 5.0.0.36528. This update includes various memory optimizations, and we believe it may help resolve the problem you are experiencing. You can easily update your system using the in-client update credentials provided below:
Build Number: 36528
Password: t70bgtIf the issue persists even after this update, please don't hesitate to let us know. We would appreciate it if you could share a memory dump with us, so we can investigate further. In such a case, we will convert this topic into a support ticket and continue our communication in private.
Thank you for your cooperation and patience as we work together to resolve this issue.
Best regards.
Post is closed for comments.
Comments
3 comments