Thanks weidong!

After I changed to httpclient3.1, it use much less time(less than 1 second) to 
start connection for Jmeter, for httpclient 4 (default http implementation for 
jmeter) is about 5 seconds. So it is bug of httpclient 4?

Thanks,
Roy
From: 张为东(为东) [mailto:[email protected]]
Sent: Thursday, May 21, 2015 9:22 PM
To: 'JMeter Users List'
Subject: 答复: What's the logic of jmeter warm up before send the first request

You can try to change the configuration “Implementation” as “HttpClient3.1” in 
http sampler.
[cid:[email protected]]

发件人: Zhang, Roy [mailto:[email protected]]
发送时间: 2015年5月20日 17:46
收件人: [email protected]<mailto:[email protected]>
抄送: Zhang, Roy
主题: What's the logic of jmeter warm up before send the first request

Hi All,

I found when I start Jmeter, after click start request button, it will take 
about 5 seconds to send the first request. It will take tiny time to send the 
successive requests. Or after some time (e.g, 5 mins) after I send the last 
request, it will also take about 5 seconds to send the next request. I think 
jmeter use this “5 seconds” for warm up before send the request, but I don’t 
know the details. Could you please tell me the details/reasons or correct me if 
my assumption is wrong? Please feel free to let me know if you need additional 
info. Thanks in advance!

The following is the jmeter test result and wireshark result screenshot, from 
the jmeter output, it send the request at 02:28:22, but from the wireshark, it 
begin to establish TCP/IP connection at 02:28:27 (about 5 seconds later).
Note: 10.6.115.217 is the windows server IP  installed with jmeter, 10.6.115.66 
is application server IP, the protocol is https.

[cid:[email protected]]

Thanks,
Roy

Reply via email to