My requirement is to hit a server request with 1000 concurrent users. When I did a sample load run with 100 concurrent threads(All threads start at the same moment), I observed that the "load time" is linearly increasing from the first sample to 100th sample. When I sniffed JMeter traffic using Fiddler, the load times are varying for most of the samples.

This variation is rising with the number of concurrent threads. For the 100 threads criteria,

  1. The difference between the maximum response times in both tools is 1.654 seconds.
  2. The difference between the minimum response times in both tools is 612 milliseconds.

JMeter is always showing higher response times. Sometimes the difference is reaching 5+ seconds.

I'm unable to pinpoint the reason behind this. Is it the fault of Fiddler or Jmeter? Difference of milliseconds is acceptable, but for many of the requests, it is multiple seconds when I increase threads above 200.

Here is how my test plan looks: Test Plan

Here is what I did:

  1. Used "Synchronizing Timer" with 100 users and 0 milliseconds for timeout
  2. Used Cookie manager and Cache manager
  3. Did not add any listener
  4. Performed load test from Non-GUI mode with below command: jmeter -n -t C:\Users\Test0304.jmx -l C:\Users\Test0304_Log_21.jtl -H -P 8888
  5. Captured Jmeter traffic from Fiddler
  6. Set JVM heap size to 6 GB (System RAM is 8 GB)
  7. No assertions, no graphs.

Additional Info:

  • Jmeter version: 3.1
  • Fiddler Version:

Please find below screenshots for reference of differences: Fiddler Screenshot JMeter screenshot

  • I have observed this behavior not only with 1 web application but many, including google.com
    – Surya T
    Apr 11, 2017 at 11:57

2 Answers 2


I notice that the 'start time' in JMeter is the same for all of your threads but it seems unlikely your machine will spawn 100 threads instantly. You could try running with fewer threads distributed across multiple machines.

  • This is a good point. If you cannot distribute across multiple, you can set a ramp up period in JMeter whereby you define the number of seconds you give for JMeter to spawn the number of required. E.g. 20 seconds to reach required load. Oct 2, 2017 at 21:55

It is normal in my experience, Have tried to run same script twice in Jmeter?? In that case results will be different too even though you run the script in same tool.

  • Yes, I ran the script multiple times. I agree that results will vary with each run but generally in milliseconds. Every time the difference between the Fiddler and JMeter results of same execution/iteration are in multiple seconds.
    – Surya T
    Apr 5, 2017 at 9:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.