I am struggling to figure out why I am processing 1 request per second via my server. depending on if SSL is used it is worse. http localhost is really fast, (requests per second: 25776.12) If it fires off https://localhost with SSL I get about 739 per second. If it is directed to my domain it is 1 per second unless I disable ssl then I get about 146 per second.. If I direct it to my ip address I can get about the same with http and 36.84 with https. b -k -c 10 -n 1000 are the test settings. Is there something I am doing it wrong or do I need to fix something with my nginx server? I am willing to post conf too if needed!



Edited 1 time(s). Last edit at 12/12/2022 07:56AM by Itsausjjmc.

Slow load testing using ApacheBench (ab) at a rate of 1 request per second can be a useful way to assess the performance of a web server or application under low and steady traffic conditions. Slow load testing can help identify potential bottlenecks, analyze resource utilization, and detect any performance issues that may arise over an extended period.

To perform slow load testing using ApacheBench at 1 request per second, you can follow these steps:

Install ApacheBench:
Ensure you have ApacheBench installed on your system. It is typically available with the Apache HTTP Server installation. If you don't have it installed, you can download it separately or install it through your package manager.

Construct the testing scenario:
Create a list of URLs or endpoints you want to test. Consider the endpoints that represent typical user interactions or frequently accessed resources on your website or application.

Execute ApacheBench with a delay:
Use the -n option to specify the total number of requests, and -c to set the number of concurrent requests (in this case, 1 request per second). Additionally, you can include the -H option to add custom headers, if needed.

The command might look like this:

arduino
Copy code
ab -n 600 -c 1 -H "Accept-Encoding: gzip, deflate" http://example.com/
In this example, ApacheBench will perform 600 requests in total (1 request per second for 10 minutes) against the specified URL (http://example.com/) while keeping one concurrent request at all times.

Analyze the results:
Once the test is complete, ApacheBench will display various metrics, including the number of completed requests, the time taken per request, and the transfer rate. Pay attention to the response time and error rate. These results will give you insights into how your web server or application handles slow and steady traffic.
It's essential to note that slow load testing is just one part of the performance testing process. For a comprehensive assessment, consider conducting tests under various traffic conditions, including normal, peak, and stress scenarios.

Additionally, when performing load testing on a production system, ensure that it's done during periods of low user activity to avoid any significant impact on real users. Always use caution and test on non-production environments whenever possible to minimize potential risks.