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

Max web conns default #710

Merged
merged 4 commits into from Apr 6, 2016
Merged

Max web conns default #710

merged 4 commits into from Apr 6, 2016

Conversation

@DiegoRBaquero
Copy link
Member

DiegoRBaquero commented Mar 30, 2016

After a lot of testing and profiling (because I was naive) I found that it's best to keep the concurrent connections small and rotate them as they become available.

This PR sets the maxWebConns to 4 by default. Making a webseed's max request vary from 1 to 4 depending on its speed & piece length.

@DiegoRBaquero

This comment has been minimized.

Copy link
Member Author

DiegoRBaquero commented Mar 31, 2016

It's safe to merge. Damn you AppVeyor.

@feross feross merged commit 796e28a into master Apr 6, 2016
4 checks passed
4 checks passed
continuous-integration/appveyor/branch AppVeyor build succeeded
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@feross feross deleted the max-web-conns-default branch Apr 6, 2016
@feross

This comment has been minimized.

Copy link
Member

feross commented Apr 6, 2016

There's an even bigger issue that @dcposch and I just discovered with web seeds. PR incoming.

@feross

This comment has been minimized.

Copy link
Member

feross commented Apr 6, 2016

@feross

This comment has been minimized.

Copy link
Member

feross commented Apr 6, 2016

0.90.2

@lock

This comment has been minimized.

Copy link

lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.