I didn't notice any significant CPU load during either download. I'm unsure why it doesn't continue to increase.
#Filezilla ftp slow folder travseral download#
The main thing that stands out to me is the TCP window size, and time to send ACKs (keep in mind I have some networking knowledge but am in no way an expert!).Īccording to Wireshark's calculation Filezilla uses a fixed TCP window of 4194304 bytes from the very beginning, where WinSCP appears to use the more "standard" ramp up technique and hovers around 1700000 bytes once the download gets going. I've run some Wireshark traces comparing a WinSCP download and FileZilla download. (from the same SFTP source, same internet connection obv). Why is the speed less than half of what I get in FileZilla? Why is WinSCP only downloading one file at a time (in both client and script)? What am i missing, what am i doing wrong? I thought this might be in scripting/shell mode only, but the WinSCP windows client has the same (slow) performance. Yes, speed depends on internet connection, but I'm comparing both on the same connection of course :) In WinSCP, only one file at at time is downloaded, and at a slower speed. In the default settings (I never played with any settings), FileZilla downloads two files at the same time! and it's showing a much faster speed. Now, I can't script in that, but it's FAST. It works very well so far, BUT I only noticed now (now that I download more files more frequently for a task in my job): it's very slow I came across WinSCP when I searched for a scriptable free SFTP download client. I'm comparing the download speed of WinSCP (both script and client) vs FileZilla.
0 kommentar(er)
