Automatically scale the allowed number of concurrent searches to use available capacity without overloading Cribl Search.

Autoscale the Number of Concurrent Searches Allowed ​

Cribl Search runs each query against available compute capacity, which limits how many searches can run at the same time. Historically, the maximum number of concurrent searches was a static cap set by the Overall concurrent search limit on the system Usage Group. Admins typically set this cap conservatively to protect Cribl Search from worst-case workloads, which could leave compute capacity unused.

With dynamic search concurrency, Cribl Search continually measures its own CPU and memory load and adjusts the cap up or down to keep configurable headroom free. Throughput is higher when Cribl Search is idle, back-off is faster when it’s under pressure, and you spend less time tuning by hand.

Dynamic search concurrency is on by default. You can turn it on or off at Settings > Search > Limits.

Usage Group concurrent limits still apply when dynamic search concurrency is on. Dynamic concurrency replaces only the Overall concurrent search limit on the system Usage Group, and that field becomes read-only.

Leave dynamic search concurrency on unless Cribl Support or your Cribl account team asks you to turn it off. The defaults work well for most workloads.

Turn Dynamic Search Concurrency On or Off ​

You need to be a Search Admin or higher.

1. In Cribl Search, go to Settings > Limits.
2. Select or clear Enable dynamic concurrency.
3. Select Save.

If Enable dynamic concurrency doesn’t appear, dynamic search concurrency isn’t available in your deployment. Contact Cribl Support or your Cribl account team if you need help tuning dynamic search concurrency for a specific workload.

See Also ​

• Limits describes general system limits that apply alongside dynamic search concurrency.
• Usage Groups lets you set per-group concurrent search limits and other usage limits.