Elasticsearch Query Performance Tuning Language Collocations
Practise the standard verbs for diagnosing and tuning slow Elasticsearch queries.
0 / 5 completed
1 / 5
Fill in: 'We ___ slow queries in the slow log so a single wildcard search that scans every shard doesn't go unnoticed.'
We 'identify' a slow query — the standard, established Elasticsearch collocation for spotting an underperforming search. The other options aren't the recognised term here.
2 / 5
Fill in: 'A leading wildcard on a large text field can ___ the query scanning far more terms than a well-structured filter would.'
We say a leading wildcard will 'cause' excessive scanning — the standard collocation for the resulting slowdown. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ filter context instead of query context wherever relevance scoring isn't needed, so results get cached and reused.'
We 'use' context — the standard, simple collocation for choosing which clause type a query runs in. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the query profile API on a slow search to see exactly which clause is consuming most of the execution time.'
We 'run' a profile — the standard, simple collocation for executing a diagnostic tool. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ query latency percentiles over time so a slow creep in p99 gets caught before users start complaining.'
We 'track' a metric — the standard collocation for monitoring a value over time. The other options aren't idiomatic here.