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]

Reply via email to