Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using the Web Stress Tester tool from Faststream to stress-test a web request, and it has an option for keeping the connection alive.
I’ll reckon that for the usual web request (say a request to a PHP page), the connection is closed after the web server processes the request and send back. Is it accurate to say that I should not keep the connection alive for such cases?
IP session setup and tear down are expensive, hence the addition of items in HTTP 1.1 which leverage already open connections instead of establishing a new one to download additional items. You may need to take a look at the documentation from Web Stress Tester to see if this is what is being referenced. You might also way to take a look at the w3c documentation on HTTP 1.1 to familiarize yourself with the additions related to session management which come with the update.
In general, however, you would want to model your behavior as closely as possible to your actual end user behavior to make your test the best predictor possible of end user behavior in production. If you have an application which keeps sessions alive that you are modeling, then by all means enable the setting. If your application does not keep alive the current session then don’t enable the option.