> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/p/performance-testing.md). # Performance Testing The process of determining the speed, responsiveness, and stability of a computer, network, software program, or device under a workload. Performance testing is the practice of evaluating how a system behaves under various levels of load and stress. It measures key metrics such as response time, throughput, error rate, and resource utilization to determine whether the system meets performance requirements and can handle expected traffic volumes. Types of performance testing include load testing (simulating expected concurrent users), stress testing (pushing beyond normal capacity to find breaking points), spike testing (sudden traffic surges), and endurance testing (sustained load over extended periods). Tools like k6, Apache JMeter, Gatling, and Locust are commonly used to simulate client traffic and measure system behavior. For API systems, performance testing validates that API endpoints respond within acceptable latency thresholds under realistic traffic patterns. Testing should include the full request path through the API gateway to measure the overhead introduced by authentication, rate limiting, and routing logic. In serverless architectures, performance testing also helps identify cold start impacts and concurrency limits that affect real-world response times. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/p/performance-testing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.