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

[WIP] rate limit dials #228

Closed
wants to merge 4 commits into from
Closed

[WIP] rate limit dials #228

wants to merge 4 commits into from

Conversation

Stebalien
Copy link
Member

Instead of releasing the rate-limit when dialing, keep it. Dialing is the most expensive part.

@ghost ghost assigned Stebalien Jan 23, 2019
@ghost ghost added the status/in-progress In progress label Jan 23, 2019
@Stebalien
Copy link
Member Author

Closing as this demonstrates the issue but isn't the right solution.

@raulk
Copy link
Member

raulk commented Jan 23, 2019

Background: dialling wasn't honouring the alpha concurrency factor, so we ended up dialling every single peer that got reported to us in CloserPeers, then rate limited the RPCs.

10s covers the 99.9th percentile of internet RTTs.

> Aikat, J., Kaur, J., Smith, F. D., & Jeffay, K. (2003, October). Variability
> in TCP round-trip times. In Proceedings of the 3rd ACM SIGCOMM conference on
> Internet measurement (pp. 279-284). ACM.
We sort inside the queue itself but *only* if there's actually a backlog.
We may now have better candidates to query.
@Stebalien Stebalien force-pushed the fix/rate-limit-dials branch from c41f37a to ce55f94 Compare January 24, 2019 03:30
@Stebalien Stebalien closed this Jan 24, 2019
@ghost ghost removed the status/in-progress In progress label Jan 24, 2019
@Stebalien
Copy link
Member Author

Replaced with #229

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

Successfully merging this pull request may close these issues.

2 participants