Added some logging to the vanilla TCPSampler (using vanilla TCPClientImpl), it appears that protocolHandler.read() execution time is to blame It's a different socket, different SocketInputStream every time, but still some synchronization must be going on causing the response read time to inflate
-- View this message in context: http://jmeter.512774.n5.nabble.com/sample-times-reported-by-JMeter-seem-to-scale-incorrectly-with-the-number-of-threads-tp5719455p5719468.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
