-
Notifications
You must be signed in to change notification settings - Fork 503
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
advanced: Number of connections #803
Conversation
Syncthing will, however, only keep connections with the best priority; by | ||
default, TCP has better priority than QUIC, so establishing a TCP connection | ||
will cause existing QUIC connections to be closed. Connection priorities can | ||
be configured. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If its the same priority, can you have mixed transports? If no, why not. If yes, how is that represented in the UI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can indeed, and it isn't really represented in the GUI at all. Currently it shows the info about the primary (oldest) connection, and a count of additional connections, but no details on the additionals. It's available in the REST API though, so it could be represented if we wanted to.
This may be a material for a different PR, but is there something to add to https://docs.syncthing.net/users/tuning regarding the connection number? I'm asking because the commit message specifically mentions possible tweaks for low-end hardware already (see syncthing/syncthing@c6334e6). |
I can add some words |
For syncthing/syncthing#8918. (We should add a link in the GUI as well, since this setting is not only available through the advanced interface.)