-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Increase buffer sizes #4426
Comments
It's done here: https://github.com/quic-go/quic-go/blob/master/sys_conn_buffers.go Not sure how / if it works on Windows. Would be great if you could try it out. |
wireguard-go seems to directly set the socket options: https://github.com/WireGuard/wireguard-go/blob/master/conn/controlfns_windows.go No idea if that's necessary, though.
Can I evaluate this using Syncthing? |
This function is used to check the size of the buffer: Lines 16 to 25 in da410a7
You could add some logging before and after we increase the buffer, and see if the value changes. |
Judging from the debug logging, things are working as expected:
Simply tested via set QUIC_GO_LOG_LEVEL=debug
.\syncthing.exe I suspect that the speedup observed by our forum user was due to the obscenely high default buffer size of 25MB. While this is obviously too much, should we follow wireguard-go and increase our buffer to 7MB? See this commit message for more details: WireGuard/wireguard-go@f26efb6 Edit: tested with the AFD registry parameters (25MB) in place:
|
Sounds reasonable. Want to create a PR? |
This topic came up in the Syncthing forum: https://forum.syncthing.net/t/system-is-slow-on-windows-look-here/21925
I'm unsure if users really need to modify the registry or if the socket options are enough to tune the buffer sizes. After briefly skimming the code, I couldn't spot where we do this for Windows?
The text was updated successfully, but these errors were encountered: