Loading...
Loading...
Browse 4 real-world technical and behavioral interview questions about Percentiles. Review scenarios, edge cases, and architectural best practices.
Derive the mix, arrival pattern, and data distribution from production telemetry rather than assumptions, size concurrency from throughput and think time instead of guessing a user count, and report percentiles with error rates so the result means something.
Read the throughput curve first: if throughput has flattened while latency rises, you are queueing behind a saturated resource, and the job is to find which one by walking utilisation and saturation from the load generator through the app tier to the database.
A flat p50 rules out a uniform slowdown, so the tail belongs either to a subset of requests or to a queueing effect. Partition the latency histogram by instance, endpoint and tenant before naming a cause, then confirm with traces, GC logs and pool-wait metrics.
Group lines by a normalised path so that /orders/1 and /orders/2 collapse to one endpoint, compute the percentile by nearest rank on the sorted latencies, and count the lines you could not parse instead of silently dropping them.