2013-01-30, 03:16
In short:
I'm using the latest nightly build with the fix for sFTP transfers, but am finding odd issues with sFTP throughput. With some machines (actually overseas from server) the sFTP throughput in FileZilla Client is great, 900 KBps, plenty speed for most needs. However, on these machines, XBMC will only transfer at approx 150 KBps and cause a lot of buffering. Using FTP I get full speeds in XBMC, but not sFTP to the same server.
These are Windows 7 and Windows 8 x64 machines running the Jan 28th nightly. The sFTP scanner bug in Frodo prevents me from testing in that. I've also tried: netsh interface tcp set global autotuninglevel=disabled on the machines with no luck and disabled security software. Thanks
Edit: Found a link between latency and slow sFTP connections discussed below.
- sFTP throughput is reduced using a high latency connection
- Testing has ruled out: encryption processing overhead, traffic shaping and network speed issues
I'm using the latest nightly build with the fix for sFTP transfers, but am finding odd issues with sFTP throughput. With some machines (actually overseas from server) the sFTP throughput in FileZilla Client is great, 900 KBps, plenty speed for most needs. However, on these machines, XBMC will only transfer at approx 150 KBps and cause a lot of buffering. Using FTP I get full speeds in XBMC, but not sFTP to the same server.
These are Windows 7 and Windows 8 x64 machines running the Jan 28th nightly. The sFTP scanner bug in Frodo prevents me from testing in that. I've also tried: netsh interface tcp set global autotuninglevel=disabled on the machines with no luck and disabled security software. Thanks
Edit: Found a link between latency and slow sFTP connections discussed below.