Last post Apr 13, 2020 03:20 PM by bruce (sqlwork.com)
Apr 08, 2020 08:12 AM|mim|LINK
I have developed a REST API using dot net core 3.1. I developed the same using dot net core 2.2. While doing load test, I found that the REST API requests of all types and to all endpoints are limited in the following ways:
IP address - 8,300 requests per minute
Can someone help me to understand why the request is limited to 8300 requests per minute and where can I change it so that I can increase it. It seems that there is a rate limit for the number of request? Please note that I developed the app with the default
code provided and I have not added any other code that would change anything in the settings.
Thank in advance!
Apr 08, 2020 02:32 PM|bruce (sqlwork.com)|LINK
Probably a limitation of your load tester.
Apr 09, 2020 08:18 AM|mim|LINK
Thanks for replying. Do you know if IIS has a default request limit?
Apr 09, 2020 02:35 PM|bruce (sqlwork.com)|LINK
Yes, as does windows. Both have a higher default (assuming you are on a current version) than your limit, but check.
Are you seeing connections refused? Still sounds like the load tester is the issue.
Apr 12, 2020 06:46 AM|mim|LINK
I am using JMeter and it seems that it allows more than 10000 users. Any hint what could be throttling?
Apr 12, 2020 06:06 PM|bruce (sqlwork.com)|LINK
10000 users would typically be a distributed network of jmeter machines. How many users per jmeter depends on how much memory and how many cores a the jmeter machine has. In your test, it appears you are using 150 threads or so. I assume the test client
is at least a 16 core machine, 32-64 gb memory and at least 4 network cards. Then you should be able to crank up the thread count to 500 to 10000.
Apr 13, 2020 11:49 AM|mim|LINK
I have managed to understand that there is a connection time out error. I had to include a response time out of 1800000 ms for the tests to pass. So it does not seem to have anything to do with dot net core I guess.
Apr 13, 2020 03:20 PM|bruce (sqlwork.com)|LINK
sound like you might be saturating your network. a network trace should help you understand.