I have made a very simple asp.net core application with a static files binding to a folder with a video, and a html page with a video element that points to that video.
I wanted to test how many clients could stream the video at the same time. Once I hit 5 active players, the page will no longer load. So something tells me there's something somewhere that sets this limit. Can I change it anywhere?
7+ Million HTTP requests per second from a single server.
The default value is 4096.
In the API Console, there is a similar quota referred to as Requests per 100 seconds per user. By default, it is set to 100 requests per 100 seconds per user and can be adjusted to a maximum value of 1,000. But the number of requests to the API is restricted to a maximum of 10 requests per second per user.
Has a maximum of 10 concurrent connections before an HTTP 403.9 error message is returned. HTTP 403.9 returns Access Forbidden: Too many users are connected.
ASP.NET Core itself doesn't have limitations and the servers it is run on can handle a lot of connections. The problem is in how you test the server. Browsers have limits on how many connections they open concurrently to a single server. This is why manually testing with a single browser you will run into a situation where nothing is downloaded. This is to make sure a single browser won't bombard a server down with lots of connections.
You should use actual benchmarking tools to test the system since they don't have these limitations.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With