Ramp-up, steady-state, soak test, spike test, stress test — types of load tests and vocabulary for discussing results. Intermediate
0 / 10 completed
1 / 10
A load test configuration shows: "Ramp-up period: 5 minutes, target: 500 virtual users."
What does the ramp-up period in a load test do?
The ramp-up period simulates realistic traffic growth. Without it, 500 virtual users start simultaneously — an artificial spike that doesn't reflect real traffic patterns and can trigger cold-start behaviour that wouldn't occur organically.
Phase
Description
Ramp-up
Gradually increase virtual users from 0 to the target load level
Steady-state
Hold at target load — the main measurement period
Ramp-down
Gradually reduce load to observe recovery behaviour
Think time
Pause between requests per virtual user — simulates real user behaviour
2 / 10
A load test runs for 4 hours at normal production traffic levels. At the 3-hour mark, the error rate starts increasing gradually.
What type of load test would specifically be designed to detect this kind of issue?
A soak test (endurance test) runs at expected load for many hours (4–24+). It finds issues that only emerge over time: memory leaks, connection pool leaks, disk space exhaustion from log growth, and gradual performance degradation.
Test type
What it finds
Duration
Soak / endurance
Memory/resource leaks, gradual degradation
4–24+ hours at normal load
Stress
Breaking point, failure behaviour above capacity
Short — ramp up until failure
Spike
Sudden traffic burst recovery, auto-scaling speed
Short — burst then recover
3 / 10
A load test report shows these results: Error rate: 0.1% at 1,000 RPS | 1.2% at 2,000 RPS | 18% at 3,000 RPS
What does this non-linear pattern indicate?
Non-linear error rate increase is a saturation signature. The system handles load well up to ~2,000 RPS (the capacity knee), then degrades steeply. This data directly informs capacity planning — the service should be scaled before reaching 2,000 RPS in production.
Term
Meaning
saturation point
The load level at which the system runs out of capacity and degrades non-linearly
capacity knee
The inflection point on the error rate / latency curve where degradation accelerates
capacity planning
Using load test results to determine when to scale out before production load hits the knee
4 / 10
A performance engineer says: "We ran a spike test by injecting 10× normal traffic for 30 seconds."
What does a spike test validate?
A spike test injects a sudden, extreme traffic burst then removes it. It tests: does auto-scaling respond fast enough? Does a circuit breaker trigger? Does the system shed load gracefully or fail completely? Does it recover after the spike ends?
What a spike test validates
Key vocabulary
Auto-scaling reaction time
auto-scaling latency — how fast new instances spin up
Overload handling
circuit breaker, shed load, rate limiting
Recovery behaviour
recovery time — how long until normal after spike ends
Resilience under surge
surge — sudden demand spike event
5 / 10
A load test plan states: "300 virtual users with a think time of 2 seconds between requests."
What is "think time" in load testing?
Think time prevents unrealistic "virtual user request storms". Without think time, each of 300 virtual users sends requests as fast as possible — that's not how real users behave. Think time = pause between requests, simulating the time users spend reading content.
Term
Meaning
think time
Simulated pause between requests per virtual user — models real user behaviour
pacing
The rate at which virtual users start new iterations (related to but distinct from think time)
concurrency vs. arrival rate
Concurrency = active users at once; arrival rate = new users per second — both shaped by think time
realistic load simulation
Configuring think time and pacing to match observed real-user behaviour patterns
6 / 10
During a code review of the load test script, Sarah comments: 'The ramp-up period is set to 5 minutes. This means we'll gradually increase the number of virtual users over that time.' What is the primary purpose of this ramp-up period in a load testing scenario?
The ramp-up period is crucial because it simulates a realistic scenario where users gradually join the system. Setting it too quickly can overwhelm the server before it's properly initialized and warmed up, leading to inaccurate results. A gradual increase allows for monitoring system performance during this initial phase.
7 / 10
Mark, a QA engineer, sends the following Slack message: 'Load test failing – API endpoint /users returns 503 errors at 1000 RPS. Looks like we need to investigate resource contention.' What is Mark *most likely* referring to when he mentions 'resource contention'?
Resource contention describes a situation where multiple processes or threads compete for limited system resources like CPU, memory, or I/O. This often manifests as errors when an API endpoint is overloaded, as the server struggles to handle the simultaneous requests efficiently – insufficient memory would be a direct cause.
8 / 10
In a PR description for a new load test script, David writes: 'This script will simulate 200 users accessing the product catalog page concurrently. We'll use a think time of 5 seconds to mimic realistic user behavior.' What does the term 'think time' represent in this context?
Think time is the artificial delay inserted between requests made by each simulated user. It's essential for producing more realistic load tests that mirror how real users interact with a system – without it, users would send requests so quickly they'd overwhelm the system and produce misleading results.
9 / 10
During a daily standup meeting, Alex reports: 'We conducted a soak test overnight to ensure our application can handle sustained load. The server CPU utilization remained consistently below 70% for the entire 24-hour period.' What type of load test was Alex performing?
An endurance test is specifically designed to assess a system's ability to sustain a consistent level of load over an extended period. The goal is to identify potential stability issues that might not be apparent during shorter tests – soaking the system for 24 hours allows it to reveal problems related to memory leaks, resource exhaustion, or long-running processes.
10 / 10
A load test report shows the following: Response Time (95th Percentile): 2.1 seconds | Throughput: 800 requests/second. What does this data primarily suggest about the system's performance?
This data suggests significant bottlenecks. A high percentile response time (2.1 seconds) combined with a throughput of only 800 requests per second indicates that the system is struggling to process the load efficiently. Optimization efforts are clearly warranted to improve both response times and overall capacity.
What will I practise in "Load Testing Vocabulary"?
This module focuses on Performance Profiling — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Performance Profiling exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around performance profiling — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Performance Profiling exercises?
See the Performance Profiling hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.