Load testing
Load testing is the evaluation of a system’s behavior, performance, and capacity under specified or simulated workloads.
ScyllaDB in Action
Load testing is the technique of applying representative or increasing workload to a system to evaluate its performance, behavior, and capacity limits.
- How it is used
- Determines cluster traffic capacity for sizing and makes monitoring dashboards display realistic load.
- How deep it goes
- Walks through schema-based YAML setup, workload tuning, ramp-up execution, and throughput and latency result interpretation.
- Examples
- Uses an article_summaries_by_date YAML profile, a 1,000-to-1 read/write run, result tables, and a Grafana overview dashboard.
- What you can do after
- Operate/configure cassandra-stress against a schema and evaluate throughput and latency while increasing database load.
Think Like a Software Engineering Manager
Load testing is software performance testing that evaluates behavior under specified levels of concurrent or simulated workload.
- How it is used
- Checks capacity and failure points under normal and anticipated peak traffic as part of software testing before release.
- How deep it goes
- Defines simulated customer load and its diagnostic aims, but gives no procedure for generating traffic or setting thresholds.
- Examples
- Uses sample-customer traffic and a million-customer video-download scenario to distinguish capacity questions from performance measurements.
- What you can do after
- Evaluate/understand whether expected peak traffic exposes capacity limits, bottlenecks, or single points of failure.
Read how Think Like a Software Engineering Manager explains load testing →
Enterprise RAG
Load testing is the practice of exercising a system with simulated traffic to measure behavior, capacity, and failures under specified demand.
- How it is used
- Validates a deployed RAG service against concurrent traffic before real users encounter failures.
- How deep it goes
- Builds a Locust WebSocket workload, instruments functions, reads live metrics, and links diagnosed failures to scaling actions.
- Examples
- Uses a Python locustfile that repeatedly sends a JSON question over a secure WebSocket and records timed actions.
- What you can do after
- Operate/configure Locust tests, interpret latency and failure evidence, and scale the constrained application component.
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
A load test is a controlled test that generates workload to evaluate system behavior under specified demand.
- How it is used
- Evaluates how synchronous web traffic or asynchronous queue work drives AWS resources and scaling policies.
- How deep it goes
- Demonstrates workload generation, command parameters, alarms, and scaling observation, without developing broader benchmarking methodology.
- Examples
- Uses a 500,000-request WordPress test and a 250-message URL-to-image queue test.
- What you can do after
- Apply it via Apache Bench and AWS consoles to trigger, monitor, and clean up scaling experiments.
Build High Value Software Systems
Testing that evaluates system behavior and performance under a specified workload.
- How it is used
- Uses load testing as an early quality check to catch performance problems before they reach production.
- How deep it goes
- Describes automated triggers, realistic query volumes, query-time thresholds, and lock detection, without detailing test implementation.
- Examples
- Uses database changes, realistic query volumes, threshold failures, and a table-lock rollback as concrete examples.
- What you can do after
- Operate a build gate that runs load tests for selected database changes and flags slow queries or locks.
Read how Build High Value Software Systems explains load testing →
LLMs in Production
Load testing is a performance-testing technique that evaluates how a service or system behaves under an expected or increasing workload.
- How it is used
- Evaluates whether a service can sustain expected or peak workload before production release.
- How deep it goes
- Defines a staging-to-analysis workflow and measures latency, throughput, TTFT, and TPS under increasing demand.
- Examples
- Demonstrates a Python Locust script, CSV metric logging, and a 50-user run that reveals a requests-per-second bottleneck.
- What you can do after
- Diagnose capacity limits and estimate replicas using latency, throughput, TTFT, and TPS measurements.
Build Financial Software with Generative AI (From Scratch)
Load testing is nonfunctional testing that evaluates an application's behavior and performance under simulated user or request loads.
- How it is used
- Uses simulated API traffic to assess responsiveness, bottlenecks, and capacity during development and deployment planning.
- How deep it goes
- Walks through Locust setup, endpoint scripting, dashboard configuration, randomized inputs, and assertions, but leaves richer API data for later.
- Examples
- Exercises a FastAPI file API through Locust tasks, randomized path parameters, response assertions, dashboard runs, and server logs.
- What you can do after
- Operate Locust to script API workloads, run simulated users, inspect metrics, and diagnose failing status codes or routing behavior.
Read how Build Financial Software with Generative AI (From Scratch) explains load testing →
Also covered in
- Write Powerful Rust Macros
- .NET in Action, Second Edition
- The Art of AI Product Development
- Kafka for Architects
- Build an AI Agent (From Scratch)
- AI Model EvaluationIn early access (MEAP)
- Data-Oriented Programming in JavaIn early access (MEAP)
- Practices of the Python Pro
- The Well-Grounded Python Developer: How the pros use Python and Flask
What to know first
- deployment pipelineA deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- productionProduction is the live operational setting in which a deployed software system serves its intended users or processes real workloads.
- memory boundA workload is memory-bound when its performance is limited primarily by memory access or data-transfer capacity rather than computational throughput.
- throughputThroughput is the rate at which a system processes or completes work, data, or requests over a specified period.
Related concepts
- Locustuses · Locust is an open-source load-testing tool for defining simulated user behavior and generating configurable concurrent traffic to measure software-system performance.
- software testingkind of · Software testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
- performance testingkind of · Performance testing evaluates a system’s responsiveness, throughput, scalability, stability, or resource use under specified workloads and operating conditions.
- cassandra-stressuses · cassandra-stress is a command-line benchmarking utility that generates database workloads for measuring Cassandra-compatible systems.
- definition of donepart of · A definition of done is an agreed set of criteria that work must satisfy to be considered complete.
Questions about load testing
What is load testing?
Load testing is the evaluation of a system’s behavior, performance, and capacity under specified or simulated workloads.
Which Manning books explain load testing?
ScyllaDB in Action, Think Like a Software Engineering Manager, Enterprise RAG, Amazon Web Services in Action, Third Edition: An in-depth guide to AWS, Build High Value Software Systems, LLMs in Production and Build Financial Software with Generative AI (From Scratch).
What should I know before learning load testing?
Manning books that teach load testing usually introduce deployment pipeline, production, memory bound and throughput first.
What kinds of load testing are there?
Kinds of load testing include browser-based load testing.
What is load testing a kind of?
Load testing is a kind of software testing. Software testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
What is load testing part of?
Load testing is part of definition of done. A definition of done is an agreed set of criteria that work must satisfy to be considered complete.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.






