response time is not real

Gatling (Open-Source)
1

i have a rest api that takes max 150 ms but when i run it in gatling it takes always 1 second.
is there something i need to configure?

2

There’s no reason for such a difference.
Just beware that Gatling accounts for DNS lookup and connection establishment

3

I have used gatling for few rest api load tests and didn’t see response time differences. It could be that when you were running your tests, maybe some other process was running on server.

4

what do you mean my your last sentence?

5

i understand, but i have checked in the same time:

  1. by rest api chrome tool
  2. gatling
    and still see that gatling give me 1 second
6

okay i have found the reason:
in my api i need to use also authorization.
there are 2 authorization mechanisms:

  1. digestAuth
  2. basicAuth

i have started with the digest one and so i have got up than 1000 ms.
when i switch to the basic one it starts shows me the correct and expected results.
and actually we use the basic one in our jmeter. so the basic must be used and not the degest.
the digest is more complex and so take higher response time.

here is a good article on the diff between those 2:
http://mark-kirby.co.uk/2013/how-to-authenticate-apis-http-basic-vs-http-digest/

7

Glad you found an explanation.
Yet, the much higher response time seems fishy.