milvus_queue_time

When Milvus transitions from index building to concurrent searches, CPU usage spikes significantly (from ~21 cores to 28 cores peak), creating a temporary bottleneck that queues subsequent requests and increases in-queue latency.

Search requests with very large NQ (number of queries per request) monopolize query node resources for extended periods, causing other concurrent requests to queue and experience elevated latency even though per-vector processing time remains normal.