You may also want to check if ipv6 dns queries are failing because the server or your proxy does not allow them so some need to wait for the timeout before some transactions will continue? You may need to permantly disable ipv6 to resolve the issue.
On 26 Sep 2017 21:30, Bob Small <[email protected]> wrote: As well as traceroute (tracert) command line and see if the hops report errors to the end point. Bob Small<mailto:[email protected]> QA Automation Development Blackboard Transact T: 602.752.6301 blackboard.com/transact<https://blackboard.com/transact> [BbTS-logo-email]<https://blackboard.com/transact> From: Bo Bodnar [mailto:[email protected]] Sent: Tuesday, September 26, 2017 12:02 PM To: JMeter Users List <[email protected]> Subject: Re: Max times values are very High Now we've details as to the experiments. Perhaps, you're seeing network issues? I'd run something like t-shark or wireshark on the computer running jmeter and see what it shows. Out network guru has seen something like this happen very infrequently during controlled experiments. The root cause was either a misconfigured switch or router in the core network. I've also seen similar things with optic networks where the laser in the NIC begins to degrade; a symptom is a burst of TCP timeouts. BB Bohdan L. Bodnar Lead Performance Engineer 1-312-871-5163 ________________________________ E-mail: [email protected]<mailto:[email protected]> 222 South Riverside Plaza Chicago, IL 60606 United States [Inactive hide details for Sumit Verma ---09/26/2017 01:48:24 PM---Hi Bob, Thanks for responding.]Sumit Verma ---09/26/2017 01:48:24 PM---Hi Bob, Thanks for responding. From: Sumit Verma <[email protected]<mailto:[email protected]>> To: JMeter Users List <[email protected]<mailto:[email protected]>> Date: 09/26/2017 01:48 PM Subject: Re: Max times values are very High ________________________________ Hi Bob, Thanks for responding. We are using New Relic to monitor service timings. At service end, I could not find any request with time > 800 ms. But at client(Jmeter) end, some requests are surprisingly taking more than 10 seconds. Could it be limitation of Jmeter? Thanks, Sumit On Tue, Sep 26, 2017 at 9:45 PM, Bob Small <[email protected]<mailto:[email protected]>> wrote: > What is the socket timeout set for? Is the service taking a very long > time using queuing or a long time for data look up? There could be many > reasons for this, I would suggest working with development to track the > long transaction time. Also logs would help if you use spluk or kibana > this may help diagnosis the issue. > > Bob Small > QA Automation > > Development > Blackboard Transact > > T: 602.752.6301 > blackboard.com/transact > > > > -----Original Message----- > From: Sumit Verma [mailto:[email protected]] > Sent: Monday, September 25, 2017 11:35 PM > To: [email protected]<mailto:[email protected]> > Subject: Max times values are very High > > Hi, > > I have run a performance tests for my service. I can see response times at > my service ends are well within 1 sec but in the Jmeter aggregate reports > max time values are very high(more 60 secs). > > What could be the reasons for such high numbers? > > Thanks in Advance. > Sumit Verma > This email and any attachments may contain confidential and proprietary > information of Blackboard that is for the sole use of the intended > recipient. If you are not the intended recipient, disclosure, copying, > re-distribution or other use of any of this information is strictly > prohibited. Please immediately notify the sender and delete this > transmission if you received this email in error. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [email protected]<mailto:[email protected]> > For additional commands, e-mail: > [email protected]<mailto:[email protected]> > This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error. The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
