Question

NeoLoad: wrong response times ?

  • 24 November 2023
  • 2 replies
  • 48 views

Hello,

we have a problem with the results of a simple web request load test.

The testobject is really simple: one simple get request (REST) with very little payload. The test runs via http-port 80.

Running the request from the load generator with postman reports a response duration of roundabout 100ms.

Running the request with NeoLoad reports always response times greater 1 second.

We have no thinktimes but pacing time 140 seconds per request (yes, very small load...).
The population is configured with ‘unlimited’ WAS emulation.
The scenario ramps up 1 to 5 User (yes: very, very small load…).

During the test run, we monitored the requests on the server. The responses leave the server after roundabout 50ms.

After all, i cannot believe in the reportes response times form NeoLoad.

 

Any ideas ?

Best regards,

Manfred Schmidt


2 replies

Some additional information:
The header-tag ‘connection’ is set to ‘keep-alive’. When i switch this tag to ‘close’, the response times in Postman and NeoLoad are the same.
Is it possible that NeoLoad ignores this setting and always forces the server to close the connection after each request (regardless of the content of the ‘Connection’.Tag)?

 

Userlevel 1
Badge +1

Some additional information:
The header-tag ‘connection’ is set to ‘keep-alive’. When i switch this tag to ‘close’, the response times in Postman and NeoLoad are the same.
Is it possible that NeoLoad ignores this setting and always forces the server to close the connection after each request (regardless of the content of the ‘Connection’.Tag)?

 

It might be too late but could you check in NeoLoad user path if you had the Reset connection option set to Auto or Yes at the Actions container level?

If you had one of them try again with that option set to “No”. Otherwise NeoLoad reset connections between each iteration and it’s like having “Close” HTTP header.

Reply