Is there a difference in speed between an HTTP transfer and an FTP transfer?

Question

Hi all. I have about 4 years experience in application programming but lately I've been getting into web and networking. My situation is that I have two servers running, an HTTP server and an FTP server. There are quite a few large files that I want to upload, and since they are large, users will obviously appreciate a fast transfer speed while downloading them. So I was wondering whether it would be better to put these large files on my FTP server or my HTTP server, depending on which one would offer a faster transfer speed.

I understand that both FTP and HTTP (application layer protocols) rely on TCP as their transfer layer protocol and this in turn relies on IP, so there shouldnt be much difference in the connection speed since FTP and HTTP both rely on the same lower protocols.

From memory packet segmentation also occurred at the transport layer (TCP) or Network Layer (IP) so there shouldnt be a difference there either. However, I'm thinking that there may be a difference in how much data is passed from the application layer (HTTP / FTP) to the Transport layer and lower, which may cause a difference in transfer speeds.

Does anybody have any info about this?

Thanks in advance

Answer 1

Set up a TFTP server and use UDP to send the files....

it will be faster than using TCP for FTP... but im not sure how much quicker..

however it is another option for you to explore as i havent experienced this myself...

however considering that your link speeds over the network will be the same for either a HTTP server or FTP server... i would go with the TFTP server.. as it will, in theory, be faster than all other options due to the lower overhead of the UDP being used...

Answer 2

Essentially, FTP was created to make the transfer of files easier and HTTP was the pioneer among the transfer protocols.

There are always a lot of new improvements and innovations in both that make them go one better than the other and, so, it's not really a "This one's the winner" kind of situation here.

Clients are designed, all the time to bring the innovations and improvements to the users.

The limit, of course, is the "speed of light" limitation.

You might find the links given below interesting reading.

All the best.

ST

Answer 3

I would say HTTP because many users have 'download accelerators' that make multiple connections and multiply the speed, and some users don't know how to initiate FTP transfers. As far as technical superiority, I'd say they're about the same. I think you need to consider your audience, rather than speed. Technical users would appreciate an FTP server, so they can more easily configure their client, and regular consumers would appreciate a nice shiny web-based, no configuration download.