Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Uxorious

Did anybody get anywhere with this.
I just noticed what might be the same issue.
If I just use commandline to scp a file from the server, I get great speeds.
But as soon as I start a 2nd scp at the same time, both of them tank their speeds.
martin

There's currently nothing to test.
But, please send me an email, so I can send you back a development version of WinSCP for testing. Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.
New

Where can I download BETA or EDGE versions of WinSCP to test if this issue is resolved?

If there is a way to run some debug command to generate useful logs, then please let me know how to do it and to where to submit such logs privately.
New

Buffer Optimization settings in WinSCP have no effect on this issue.
martin

Re: BBR2 congestion algorithm cripples WinSCP throughput in Windows 11

Please, let us know if the suggestion by @Guest helps.
Guest

You could try to turn off
Advanced Settings -> Connection -> Optimize connection buffer size
New

BBR2 congestion algorithm cripples WinSCP throughput in Windows 11

Windows 11 supports BBR2 congestion algorithm that can be enabled with the following commands and a reboot:
netsh int tcp set supplemental Template=Internet CongestionProvider=bbr2

netsh int tcp set supplemental Template=Datacenter CongestionProvider=bbr2
netsh int tcp set supplemental Template=Compat CongestionProvider=bbr2
netsh int tcp set supplemental Template=DatacenterCustom CongestionProvider=bbr2
netsh int tcp set supplemental Template=InternetCustom CongestionProvider=bbr2

It works as it should for most applications, but enabling it cripples WinSCP 6.X throughput to an extreme degree. It affects both SSH and SFTP protocols, but only WinSCP is affected. It doesn't cripple throughput when used with PuTTY 0.78+. Any ideas?