Hi, In HTTP4 version used by JMeter, there is an initialization of SSLContext that takes some time, it happens even if only http is used (it is due to eager init of SSLContext which was lazily iniitliazed in HttpClient 3.1). Maybe you can create an enhancement request at httpclient project for this.
Even with this fix , maybe there should be a warmup request in JMeter to init all Http related objects. Feel free to create an enhancement request in JMeter. Meanwhile switching to HttpClient 3.1 impl may be an option. Of course this should be a minor issue as in a usual load test you have thousands of requests and having the first one being "abnormaly" long is not a big issue. But it is better to improve this. Regards @ubikloadpack On Wed, May 20, 2015 at 11:46 AM, Zhang, Roy <[email protected]> wrote: > 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. > > > > > > Thanks, > > Roy >
