Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference throttling #209

Closed
jirenius opened this issue Oct 8, 2021 · 1 comment
Closed

Reference throttling #209

jirenius opened this issue Oct 8, 2021 · 1 comment

Comments

@jirenius
Copy link
Collaborator

jirenius commented Oct 8, 2021

Issue

When Resgate subscribes to a resource (due to client subscribe requests, add events on a collection, change events on a model, etc.), it will recursively follow any resource reference for that resource.

If a lot of resources are referenced, the service(s) may be overwhelmed by requests, failing to respond within Resgate's default timeout period of 3 seconds. This will in turn result in Resgate setting the references to a system.timeout error for any timed out resource.

Solution

It should be possible to throttle the number of concurrent requests being sent when following resource references. This can be done by introducing a single integer configuration value:

  • referenceThrottle - integer value telling how many concurrent requests to have running at the same time when following resource references for any single resource subscription.
@jirenius jirenius changed the title Throttling reference following Reference throttling Oct 8, 2021
jirenius added a commit that referenced this issue Oct 8, 2021
jirenius added a commit that referenced this issue Oct 11, 2021
…tling

Feature/gh 209 reference throttling
@jirenius
Copy link
Collaborator Author

Resolved in RP #210

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant