Skip to content
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

Open
IgorA100 opened this issue May 28, 2024 · 5 comments
Open

Todo: Requires preventing server CPU overload #4049

IgorA100 opened this issue May 28, 2024 · 5 comments

Comments

@IgorA100
Copy link
Contributor

Describe Your Environment

  • Version of ZoneMinder 1.37

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?

@connortechnology
Copy link
Member

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 %).

@connortechnology
Copy link
Member

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.

@IgorA100
Copy link
Contributor Author

I don't think there is anything we can do about this.

ZMC consumes the most resources
The simplest option is to stop some cameras and inform the user about the problem. Not the best solution, but it will prevent event recording from being lost.

We could switch to straight recording instead of decoding+motion detection I suppose,

Of course, this should solve some of the problems, but CPU and disk overload needs to be controlled somehow.

Would need good AI to figure out what to do.

Yes.

@connortechnology
Copy link
Member

There is a per-monitor setting about Importance. Could kill off unimportant monitors.
People should have monitoring setup to alert them of these problems and then they need to provision more hardware. We can't be psychic.,

@IgorA100
Copy link
Contributor Author

I probably didn't express my thoughts quite correctly.
I'm not suggesting stopping cameras completely.

  1. I think the most important point is recording events to disk. In this case, the server administrator must ensure the necessary performance.
  2. As a rule, server overload occurs during online viewing, i.e. Watch or Montage page. I suggest stopping the cameras when watching, but making sure they continue recording.

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%.
Thus, when viewing 7 cameras, the load on the server will be 100%.
It is necessary to disable live viewing of 1-2 cameras. But continue from the recording if it was made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants