[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


DOS Ftp throughput vs Windows Ftp client throughput

Posted on 2005-04-07
Medium Priority
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
  • 3
LVL 40

Accepted Solution

Fatal_Exception earned 900 total points
ID: 13726052
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

ID: 13726161
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.

Assisted Solution

fixnix earned 600 total points
ID: 13740608
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 www.sysinternals.com) 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

ID: 13740944
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

ID: 13751959

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

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 …
This is the first one of a series of articles I’ll be writing to address technical issues that are always referred to as network problems. The network boundaries have changed, therefore having an understanding of how each piece in the network  puzzl…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…

873 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