Currently, we are trying to load test our API’s against 4000 TPS. In the httpRequestBuilder, I have added check for response time to be less than 3000ms. We also record integration and response latency of the request in our API gateway logs. So, when we execute the test, we have some requests taking greater than 3000ms, but in our API gateway logs it takes less time.
So, what may be the reason for this irregular response time in gatling?
It’s not really for us to say Gatling is just the messenger here, it shows the response time it receives. It could be any of the below or other issues:
Networking
Proxy
DNS
TLS
etc.
With Gatling Enterprise you can get additional metrics that can help you narrow down the cause (TLS duration, DNS resolution, etc.) but with the information here we can’t be too sure as we don’t know anything about the application/environment.
Hi @slandelle , we are running on an AWS EC2 instance and also in the same region where our services are running. So that, it is strange for us to get some inconsistent response time in gatling because there should not be any network latency also.