DOS Ftp throughput vs Windows Ftp client throughput

Posted on 2005-04-07
Last Modified: 2008-01-09
Why is there a difference between the throughput speed when downloading a file using an ftp session in DOS versus a windows client like ftp commander. I am using a XP machine as client and a linux ftp server totally isolated from the LAN to perform this test. On average I get 11M/s when using DOS for a file size of 70M, with any windows based ftp client like FTP Commander I get 3.2M/s for downloading the same file.
Question by:Stars
    LVL 40

    Accepted Solution

    I might suggest that your packet sizes are different, which could produce less latency in the devices (internet switches and routers) as they travel across the Ether.  Also, GUI based downloads have more overhead as the packets come up the OSI model, and through the Application Layers..  Just my theory on this, and I could be wrong..


    Author Comment

    The routers and switches are out of the question, I am using a cross cable from client pc directly to the ftp server, your theory about the overhead with a windows gui might be right. Lets see if we get other explanations.
    LVL 9

    Assisted Solution

    I noticed the same behaviour many years ago and never thought to question why....GUI applications will almost certainly have bloat by orders of magnatude over the same functionality performed via a CLI.  I haven't done this, but you may want to load up process explorer (free from and run your ftp.exe, and look at what .dll's and handles are related to ftp.exe during your transfer, then do the same with your preferred GUI client.  The bloat factor should be quite apparent.  

    This isn't really an exact answer, per-se, but it's a method to see what's going on inside your system and what resources are being used...and after seeing it for yourself you'll probably no longer wonder why there is such a speed difference :).
    LVL 40

    Expert Comment

    Yea, if it is a direct connect, then latency is definitely not the issue...  I still go with the GUI overhead, as referred to by fix as bloat..   But running a process explorer should also help identify it..  

    You might even try ethereal to watch the packets (frames) as they go out your NIC...  You can then see what type of overhead the gui is putting on the packet sizes...
    LVL 40

    Expert Comment


    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Join & Write a Comment

    Nslookup is a command line driven utility supplied as part of most Windows operating systems that can reveal information related to domain names and the Internet Protocol (IP) addresses associated with them. In simple terms, it is a tool that can …
    The Need In an Active Directory enviroment, the PDC emulator provide time synchronization for the domain. This is important since Active Directory uses Kerberos for authentication.  By default, if the time difference between systems is off by more …
    This video is in connection to the article "The case of a missing mobile phone (". It will help one to understand clearly the steps to track a lost android phone.
    In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor ( If you're interested in additional methods for monitoring bandwidt…

    745 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now