![winscp vs filezilla speed winscp vs filezilla speed](https://media.bitdegree.org/storage/media/images/2019/11/Best-FTP-Client-WinSCP.png)
- #Winscp vs filezilla speed download#
- #Winscp vs filezilla speed free#
- #Winscp vs filezilla speed windows#
Note that there are still plenty of ACKs being sent back throughout the cycle - about 1 ACK reply per every 2 packets received. This repeated cycle takes consistently 0.017s, giving about 7.7MBps, or 61Mbps.
![winscp vs filezilla speed winscp vs filezilla speed](http://4.bp.blogspot.com/-etkveg0rkuo/VETlxfADnfI/AAAAAAAABLQ/Bo-lUBNVHT8/s1600/3.png)
#Winscp vs filezilla speed download#
The FileZilla download takes 90 packets of 1460 bytes, and 1 packet of 184 bytes for a total of 131584 bytes (I don't know why it doesn't fill out the entire 4194304 window but as I understand it doesn't necessarily HAVE to). It's a bit hard to show plots of SEQ/ACK response time, but in Wireshark there is a SEQ/ACK analysis field that gives "RTT to ACK the segment" and FileZilla was consistently around 0.00002s whereas WinSCP seemed to be a lot more inconsistent, ranging from 0.00004s up to 0.00007sįurthermore, looking more closely at the way the packets are coming in, both downloads follow the pattern of receiving "full" packets of 1460 bytes, until there is one final smaller packet (assuming this is the end of the TCP window), before repeating. I also tried alternating between AES and Blowfish encryption in the WinSCP options but this didn't make any difference (FileZilla uses AES by default). I didn't notice any significant CPU load during either download. I'm unsure why it doesn't continue to increase. 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?
#Winscp vs filezilla speed windows#
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. So i downloaded two files totalling 50MB. 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
#Winscp vs filezilla speed free#
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.