Hi Peter, >From my second point I want to say, you should have to test from Jmeter from machine having high RAM.
Find test result from my machine. [image: Inline image 1] Many Thanks Sagar On Tue, Jan 26, 2016 at 7:16 PM, Peter Peterse <[email protected]> wrote: > Hello Sagar, > > Thanks for your reaction. > When I run it in the non-gui the load times are similar to the gui. > I'm not sure what you mean with your second point. Running JMeter on the > server which you want to test? This is not a good idea. I always create my > load test on my local machine. The first test are also on this machine. > > My example load test can be downloaded from: http://we.tl/qL5gsBmuR2 > This test contains only a requests which is similar to the requests in my > own test, and has the same issues. Load times costs 500ms in stead of less > than 200ms. > > Regards, > Peter > > > Op 26-1-2016 om 11:56 schreef SAGAR JISKAR: > > Hi Peter, >> >> Try below possible methods >> >> 1) Run this test in NON GUI mode. >> 2) Jmeter should have installed on server not on local machine. >> >> Many Thank >> Cheers, >> Sagar Jiskar >> >> >> >> On Tue, Jan 26, 2016 at 6:26 PM, Peter Peterse < >> [email protected]> >> wrote: >> >> Hello all, >>> >>> I'm seeing some rare issues with the load time in JMeter (2.13) when I >>> create a test which loads json requests. >>> For example I create the next test plan: >>> - Test plan >>> - Thread Group >>> - HTTP Request >>> servername: suggestqueries.google.com >>> portnumber: 80 >>> protocol: http >>> method: GET >>> path: /complete/search?q=ob&client=jsonp&hl=fr >>> - HTTP Header Manager >>> Content-Type = application/json; charset=utf-8 >>> - View Result Tree >>> >>> The request in the View Result Tree looks like: >>> ====== >>> GET >>> http://suggestqueries.google.com/complete/search?q=ob&client=jsonp&hl=fr >>> >>> [no cookies] >>> >>> Request Headers: >>> Connection: keep-alive >>> Content-Type: application/json; charset=utf-8 >>> Host: suggestqueries.google.com >>> User-Agent: Apache-HttpClient/4.2.6 (java 1.5) >>> ====== >>> >>> The sampler result is: >>> ====== >>> Thread Name: Thread Group 1-1 >>> Sample Start: 2016-01-26 11:08:51 CET >>> Load time: 551 >>> Connect Time: 8 >>> Latency: 551 >>> Size in bytes: 459 >>> Headers size in bytes: 383 >>> Body size in bytes: 76 >>> Sample Count: 1 >>> Error Count: 0 >>> Response code: 200 >>> Response message: OK >>> >>> Response headers: >>> HTTP/1.1 200 OK >>> Date: Tue, 26 Jan 2016 10:08:51 GMT >>> Expires: Tue, 26 Jan 2016 10:08:51 GMT >>> Cache-Control: private, max-age=3600 >>> Content-Type: text/javascript; charset=ISO-8859-1 >>> Content-Disposition: attachment; filename="f.txt" >>> Server: gws >>> X-XSS-Protection: 1; mode=block >>> X-Frame-Options: SAMEORIGIN >>> Accept-Ranges: none >>> Vary: Accept-Encoding >>> Transfer-Encoding: chunked >>> >>> >>> HTTPSampleResult fields: >>> ContentType: text/javascript; charset=ISO-8859-1 >>> DataEncoding: ISO-8859-1 >>> ====== >>> >>> In this case the load time is 551ms. >>> When I execute the same request in FireFox Firebug gives me a loadtime of >>> 187ms. >>> I find it a huge gap between JMeter and Firebug. >>> >>> Can someone give me a clue what I can do to get a valid load time in >>> JMeter? >>> >>> Thanks for the reactions. >>> >>> Regards, >>> Peter Peterse >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
