Hello, I recently recorded my application with JMeter.
- The application is SSL-enabled. - Application launch, login, and a screen launch are inside a Once-Only Controller. - The actual *transaction*- which involves just one POST request- is in a separate transaction controller. - Sleep time of 1 second is configured. I have been running 1 VU tests, and I have observed that (for the *transaction* alone): 1. While running with think time, average response time is about 42 ms. 2. While running without think time, average response time is 31 ms. To eliminate latency and excess load, I am running only 1 VU tests for 30-60 seconds on the same machine that hosts the application. I have observed (via netstat) that JMeter opens a new connection every 2-3 seconds and I believe the overhead of new handshakes plus the SSL handshake (and other connection-related processing) is the reason between this difference. I have not seen this behavior with other tools like NeoLoad and OATS. In those tools, when an application that has sessions is run in a load test, there is only one socket (connection) per virtual client and it remains open throughout the run. Is there any way to ensure that JMeter does not open new sockets for new requests in the middle of the run like this? Keep-alive is enabled for HTTP requests. -SK
