You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all requests are served in the order they are received. Currently if the server is under heavy load and the client has sent prefetch requests in the login screen, when the player logs in the client will have to wait until the prefetch requests are fulfilled before it receives the priority request files.
How imporant is this feature?
What is the maximum amount of files a client can request in a set timeframe? Will that amount ever exceed the server's throughput even if it's at 125% capacity? (2.5k connections)
Solution
Read X amount of requests per client and serve the priority requests first
Side-effects
Request limits, back-pressure and load balancing will have to be handled more manually rather than leaving it to suspending io and coroutines.
The text was updated successfully, but these errors were encountered:
Currently all requests are served in the order they are received. Currently if the server is under heavy load and the client has sent prefetch requests in the login screen, when the player logs in the client will have to wait until the prefetch requests are fulfilled before it receives the priority request files.
How imporant is this feature?
What is the maximum amount of files a client can request in a set timeframe? Will that amount ever exceed the server's throughput even if it's at 125% capacity? (2.5k connections)
Solution
Read X amount of requests per client and serve the priority requests first
Side-effects
Request limits, back-pressure and load balancing will have to be handled more manually rather than leaving it to suspending io and coroutines.
The text was updated successfully, but these errors were encountered: