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, there is a single queue for all users per API endpoint to manage throttling. This setup allows a single user to flood an endpoint with requests, leading to performance degradation for the API experienced by other users. To address this, we propose binding the throttling mechanism to individual user sessions. This change aims to ensure that the excessive requests of one user do not negatively impact the API performance for others.
//Example method with timeout and queue:({timeout: 1000,queue: {concurrency: 1,size: 200,timeout: 3000,},method: async({ a, b })=>{constresult=a+b;returnresult;},});
To Reproduce
No response
Expected behavior
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Impress and Node.js versions
No response
Platform
No response
Describe the bug
Currently, there is a single queue for all users per API endpoint to manage throttling. This setup allows a single user to flood an endpoint with requests, leading to performance degradation for the API experienced by other users. To address this, we propose binding the throttling mechanism to individual user sessions. This change aims to ensure that the excessive requests of one user do not negatively impact the API performance for others.
A piece of video discussing this problem
To Reproduce
No response
Expected behavior
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: