-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Todo: Requires preventing server CPU overload #4049
Comments
I don't think there is anything we can do about this. We give the user the tools to see that their server is overloaded. (Load and CPU% and ram use %). |
We could switch to straight recording instead of decoding+motion detection I suppose, but it may be the disk IO that is the bottleneck. Would need good AI to figure out what to do. |
ZMC consumes the most resources
Of course, this should solve some of the problems, but CPU and disk overload needs to be controlled somehow.
Yes. |
There is a per-monitor setting about Importance. Could kill off unimportant monitors. |
I probably didn't express my thoughts quite correctly.
For example, there are 50 cameras. The server is configured so that when these cameras are running, the CPU load does not exceed 30%. Each camera during live viewing increases the server load by 10%. |
Describe Your Environment
When the CPU load is more than 95-97%, failures in the server operation are observed, therefore it is necessary to prevent the load from exceeding XX% (85-95??)
Yes, the user can control the CPU load himself, but when there are many users (and not just one responsible administrator), there may be problems with control. As a result, there may be failures when recording important events, and this should not be allowed.
What does anyone think about this?
The text was updated successfully, but these errors were encountered: