Load Testing for Websites and APIs

What is your Load Testing Goal?

The main goal of load testing is to see whether the application can sustain the increased load on the server or will it crash the server.

Also, to identify areas in the architecture of your application which don’t function properly, either too slow or not functioning at all.

gather the top 3 locations from where your customers access your website or web services.
find out how many users accessed your application per second
Define supported concurrent users/second, expected response time and any other client side (latency, hits/second) or server side (CPU, Memory etc) performance metrics you want to consider.
You need to determine what good performance means for your System under Test, because the system under test will start throwing errors and maybe start crashing under a heavy load of actions/concurrent users

Start with a small number of clients (1, 20, 50, 100 concurrent users / second). Try to increase the number of the clients gradually to understand how your API, Website or WebApp behaves.
Run GET requests on your main website pages (top 5 web pages)
Identify and run API Login request (usually these are POST requests made with a POST Body to an API endpoint)
Make GET or POST requests with an authenticated or non-authenticated user
Monitor for each test:
Client side: Response time, Latency time, Hits/s, Throughput/s
Server side: CPU, Memory, I/O
Errors: 4xx, 5xx, Other error codes and responses

1 min

5 cards