-
Notifications
You must be signed in to change notification settings - Fork 584
Implement process manager for C in Go #7984
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
Conversation
2eee05c
to
6600ca8
Compare
bump |
Same here. Less dependencies is better in my opinion. Have you tested this PRs performance yet? |
Yes: #8196 (comment) |
The load seems to be a quiet a bit higher with this PR. I think we need a lot of testing and code reviewing before we can decide on this. Also, even if we decide to put this into 2.13.0, we still need a fix that helps with check latency in 2.12.x. |
Well, 2x checks/time need 2x load. |
I really like this approach. Could we have some numbers for comparison of Icinga 2 w/ and w/o the Go process manager, i.e. load, latency, checks per second with 1m check interval and 1k hosts, 10k hosts, 100k hosts, 1000k hosts. |
Yes please! |
I'm sorry, but 1m checkables are too much. With our cloud's biggest boxes I could make 250k checkables with the This PR. Icinga fires almost the requested 250k/m w/ 4ms latency using about 1.0 load per CPU. v2.11.5. Doesn't even fire 100k/m and the checks jam blocks the checks for the dashboard, e.g. latency. v2.12.0. Directed by Robert B. Weide. |
Same setup as above with 25k checkables – #7984, v2.11.5, v2.12.0 |
6600ca8
to
95f5428
Compare
95f5428
to
803107f
Compare
@cla-bot check |
fixes #7600
fixes #8196
closes #7744