-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Alerting + Task Manager] Benchmarking 7.14 #95194
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Following the latest RAC leads sync (held 6th April), I think we should bump this to a later point so we can include Alerts-as-Data in the benchmarks. This does raise some questions about how we want to measure our API performance. |
It looks like ES have been able to address the issue we identified in UpdateByQuery: elastic/elasticsearch#63671 We expect this to address the degradation we've identified when there are more than 30 Kibana instances or so, so it's something we should validate at part of this issue. |
Bumped to 7.14 😬 |
The stress tester needed some updates, as ecctl has changed a bit since the last time we ran the tester, and a few enhancements have been added: commits: changes:
|
Here are three runs I made with the tester; I didn't see any significant regressions, nor any significant increase in performance - as expected
|
Following the release of 7.14 and with it the fresh perf work we've done we decided we need to do the following:
Use the results of the perf test as a basis for a sizing your Kibana cluster for alerting blogpost, similar to https://www.elastic.co/blog/benchmarking-and-sizing-your-elasticsearch-cluster-for-logs-and-metricsnote: 2021-08-09: we split item 2 off to a separate issue: [alerting] public facing doc on alerting performance #107979
The text was updated successfully, but these errors were encountered: