Ctrl K
QA · Mid-level · Theory

A load test showed that at 500 requests per second, response time grew from 200 milliseconds to three seconds. How would you track down the cause, and what would you put in the report?

~4 min by voice

How to approach it

This checks whether the candidate can systematically find a bottleneck under load rather than just noting 'it's slow'. Interviewers look at how they validate the test itself, read the metrics, go through the layers of the system (resources, database, dependencies) and frame the conclusion relative to the SLA.

Have you seen this question in a real interview?
Answers0
Avg. score—
Strong—
Practiced0
Topics
Similar questionsВ день зарплаты эндпоинт истории операций начинает отвечать по несколько секунд, а база упирается в сто процентов CPU. Как вы будете разбираться и что делать? SeniorWhy are strings immutable in Java, and why shouldn't you concatenate strings with plus in a loop? JuniorA service running on G1 periodically has pauses of one to two seconds, and it's hurting latency. What would you do, and when is it worth looking at a different garbage collector? Mid-levelYour Python script runs slowly. How will you figure out what exactly is slowing it down? JuniorAfter a release, Core Web Vitals dropped in production, primarily INP and LCP. How would you find the cause, and what do you usually end up fixing? Senior

Answer by voice

The interviewer will ask this question and listen. Think out loud and ask for a hint if you need one. When you're done, pause or tap “That's my answer”. In about a minute, your score and the points you covered show up here.

Sign in to answer

Best with headphones · ~4 min