Performance improvement has been and will be a focus for ~"group::global search". As we were considering what would be our benchmarking toolkit to measure our performance, [Rally](https://github.com/elastic/rally) stood out to be an ideal candidate to perform such tasks. This epic is created to continue our exploration of Rally and eventually set up a workflow using it for our Elasticsearch performance testing. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ## Related videos * https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right * https://www.youtube.com/watch?v=T0tRDNDjHcI ## Ideas from training * use top X slowest queries * run searches with with caching disabled (to avoid request caching) * use as many unique search terms as possible (use test length, searches/second statistics from kibana to get rough estimate of how many terms needed) * replicate production index (could be costly) * focus first iteration on project and group search performance (index needed for testing will be smaller and not required to be full production) * future iterations could include global search, indexing performance