About to checkout Gatling for load test to my REST api, any other suggestions?

So far their docs look straightforward to follow, requires scala but it doesn't look that complicated for that particular case.

Dotnet core devs, do you recommend another tool?

F5 is my favourite

But I'm actually looking to try our Gatling, so I'll 📌 this

@alexbrooklyn what are the pros of F5? my goal is to check on a given specs, how much will the server hold?

SoapUI for load testing is nice

Bombardier is my favorite. Its not complete load balance checker tool but its pretty easy to just benchmark single api endpoint. You can just download binary release and use it from command line.
https://github.com/codesenberg/...

@gitpush Quite easy to use, althought your finger will most likely get tired after a while

@alexbrooklyn @hack @Borchi Thanks guys, I ended up sticking with gatling but if I may ask, excuse my noobness, I set the test to 5 users that call two api endpoints, test results come back that each call requires 1.5 seconds?

The service and database are both running on the same laptop that the test is running is this the cause? Because when I call the actual API it takes no more than 800ms what am I doing wrong?

@gitpush I don't know what causes that problem but you can try investigating your local api with your browsers network logs to check how much time it actually takes on your local. Local environments may be slower than your test/prod environments. Also verify that you are not connected to any vpn or proxy server

@hack Thanks man I'll check but what makes me confused is, its like the service has no ability to handle load, when I add more users the time is increased in huge values, for example 10 users 10 requests/s take less than 500ms, but if I add 20 users, it takes more than 2 seconds