5 collocation exercises on performance optimisation verbs.
0 / 5 completed
1 / 5
The performance engineer will ___ the application to find where CPU time is being spent.
To profile an application means to run it under a profiler to collect data on where time and memory are consumed. Profile is the precise performance term, behind "profiling tools" like py-spy, perf, and async-profiler. Inspect up, look into, and watch over are informal and do not imply the use of a profiler. Engineers say "profile the service under load to identify hotspots," so profile the application is the correct collocation for the systematic measurement of code performance.
2 / 5
Before releasing, the team will ___ the API endpoint to measure its throughput and latency under load.
To benchmark an endpoint means to measure its performance under controlled, reproducible conditions, typically using a load-testing tool. Benchmark is the precise performance term, as in "benchmark results" and tools like wrk and Locust. Test out, time it, and check over are informal and do not carry the sense of structured, comparative measurement. Engineers "benchmark the endpoint before and after optimisation," so benchmark the endpoint is the correct collocation for measuring baseline performance.
3 / 5
The team will ___ database queries by rewriting them to use indexed columns rather than full-table scans.
To optimize queries means to rewrite or restructure them to execute more efficiently. Optimize is the standard performance verb, behind "query optimisation" and database query planners. Fix up, speed through, and make fast are informal. DBAs say "optimize the slow query by adding an index," so optimize queries is the correct collocation for improving database operation efficiency through better SQL or indexing strategies.
4 / 5
To avoid recomputing expensive computations on every request, the service will ___ the results in Redis.
To cache results means to store computed output in a fast store so repeated requests are served without recomputation. Cache is the precise performance term, behind "caching layer" and tools like Redis and Memcached. Store away, keep back, and hold on lack the technical, temporary-fast-copy sense. Engineers say "cache the results in Redis with a 5-minute TTL," so cache the results is the correct collocation for avoiding redundant computation by storing outputs close to the consumer.
5 / 5
The frontend team will ___ the heavy images and charts so they load only when the user scrolls to them.
To lazy-load resources means to defer their loading until they are actually needed, improving initial page load time. Lazy-load is the precise frontend performance term, as in "lazy loading images" and React's React.lazy(). Slow-load, late-start, and defer-load are not real technical terms. Engineers say "lazy-load below-the-fold content," so lazy-load is the correct collocation for the technique of deferring resource loading to speed up the critical rendering path.