Skip to content
This repository has been archived by the owner on Feb 1, 2023. It is now read-only.

WIP improve provider request rate limiting #138

Closed
wants to merge 1 commit into from

Conversation

hannahhoward
Copy link
Contributor

Goal

The Gateway is having issues seemingly due to getting backed up looking for more providers for requests.

Implementation

-- So far, just remove rate limit on simultaneous requests for more providers completely in this branch -- which we will deploy to the gateway to test efficacy.
-- if successful, we will decide on an optimal strategy and implement

@Stebalien
Copy link
Member

Do we ever have multiple parallel find provider requests for the same session?

@hannahhoward
Copy link
Contributor Author

@Stebalien yes we could.

@hannahhoward hannahhoward force-pushed the feat/remove-simultaneous-provider-limit branch from 820f40a to 43cbefc Compare June 14, 2019 18:32
remove rate limit on simultaneous requests for more providers

License: MIT
Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>
@Kubuxu Kubuxu force-pushed the feat/remove-simultaneous-provider-limit branch from 43cbefc to a2c78b0 Compare June 14, 2019 19:03
@hannahhoward
Copy link
Contributor Author

hannahhoward commented Jun 17, 2019

SO this seems to be doing well on the gateways... I wonder if we should move toward a merge. How processor intensive are find provider requests? If we dedup requests (already part of this code), can we just go ahead and remove the rate limit?

@Stebalien
Copy link
Member

Status:

I'd like to move this rate limiting down into the DHT itself and make it configurable on a per-node basis.

@hannahhoward
Copy link
Contributor Author

ok closing then.

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

Successfully merging this pull request may close these issues.

2 participants