Rest API request limit - Dot net core 3.1 RRS feed

  • Question

  • User-1163549808 posted

    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!

    Wednesday, April 8, 2020 8:12 AM

All replies

  • User-474980206 posted

    Probably a limitation of your load tester. 

    Wednesday, April 8, 2020 2:32 PM
  • User-1163549808 posted

    Thanks for replying.  Do you know if IIS has a default request limit?

    Thursday, April 9, 2020 8:18 AM
  • User-474980206 posted

    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.

    Thursday, April 9, 2020 2:35 PM
  • User-1163549808 posted

    I am using JMeter and it seems that it allows more than 10000 users.  Any hint what could be throttling?

    Sunday, April 12, 2020 6:46 AM
  • User-474980206 posted

    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.

    Sunday, April 12, 2020 6:06 PM
  • User-1163549808 posted

    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.

    Monday, April 13, 2020 11:49 AM
  • User-474980206 posted

    sound like you might be saturating your network. a network trace should help you understand. 

    Monday, April 13, 2020 3:20 PM