![]() ![]() It will be done using the keep alive header.Īfter the process finishes the 20 thousand requests, you will receive feedback on stats. ab -k -c 350 -n 20000 /īy issuing the command above, you will be hitting with 350 simultaneous connections until 20 thousand requests are met. By default it will hit protocol if you don't specify it. ![]() Since browsers do this and you're likely to want to simulate the stress and flow that your site will have from browsers, it is recommended you do a benchmark with this. You don't need to pass a value for -k as it it "boolean" (meaning: it indicates that you desire for your test to use the Keep Alive header from HTTP and sustain the connection). k: This does the "KeepAlive" funcionality browsers do by nature. ![]() A high -n value with a -c value that your server can support is a good idea to ensure that things don't break under sustained stress: it's not the same to support stress for 5 seconds than for 5 hours. This just decides the length of the benchmark. n: Indicates how many requests are going to be made. This is what actually decides the amount of stress your site will suffer during the benchmark. While ab runs, there will be -c clients hitting the site. Indicates how many clients (people/users) will be hitting the site at the same time. Having said that, here's the most common and simplest parameters: The Apache benchmark tool is very basic, and while it will give you a solid idea of some performance, it is a bad idea to only depend on it if you plan to have your site exposed to serious stress in production. ![]()
0 Comments
Leave a Reply. |