Home Articles Forums Gallery Marketplace Videos

WoodCentral Forums

Knowledge You Can Build On — Est. 1998

ADVERTISE HERE - FREE TRIAL

OT: FTP speed

Posts

OT: FTP speed

#1

OT: FTP speed

Orinda Dan

>My work is starting to use FTP to transfer fairly large digital images between offices. A typical set of images may be around 10-50 MB. The speed at which the files are transferred seems awfully slow. I believe our offices are linked with DSL lines. When compared to downloading similar sized files from non-FTP sites, the FTP transfer "feels" much slower on the same computer.

The IT guys who set up the system on one of our servers are new to FTP and seem to think FTP transfers are slow in nature. Is this indeed the case? If so, is there any work-around to speed up the transfer rate?

Any help would be greatly appreciated.

Dan

Re: OT: FTP speed

#2

Re: OT: FTP speed

RobV

>FTP transfers are faster than through HTTP because there is less overhead within the FTP protocol itself... sounds like something is not configured right or there is something wrong with the FTP protocol in the software you're using to implement it.

Re: OT: FTP speed

#3

Re: OT: FTP speed

wilbur

>1. Try switching to passive mode if your FTP client has active mode running, or vice versa.

2. Double check with your ISP to make sure that your upload speeds aren't capped. Most basic internet setups are such that download speeds are much faster than upload speeds, unless you specify this with your ISP.

3. Use a different protocol. You might want to consider transferring files by SSH or SFTP, since that way data transfers, including passwords will be encrypted.

Re: OT: FTP speed

#4

Re: OT: FTP speed

Ron in Drums PA

>With most ISPs, upload speeds are slower than download speeds.

Re: OT: FTP speed

#5

ADSL

Bill Howatt

>If you have DSL lines they are more properly called ADSL with the first A standing for Asymetrical. As Ron mentioned the upload speeds are much slower - think maybe around 6X or so. For most net users this isn't a problem since the amount of uploaded information is much, much smaller than downloaded.

Bill

Re: OT: FTP speed

#6

So what Bill is trying to tell you

Rob Sandow

>Is that you have 2 offices each with ADSL links to the internet. If you can download at 1.5Mbps, you can probably only upload at something like 128Kbps. Therefore, data transfers between the two sites will be limited to the lower speed. Most people don't notice this because they only use DSL to download stuff from the Internet. So if you are downloading an image from a web site, you may get 10 times the throughput as you would moving the images between sites linked with DSL. Switching to cable might help some. Cable has the same asymmetrical nature but both upload and download speeds are faster. The problem isn't FTP. FTP is actually a more efficient file transfer protocol than HTTP.

Rob

Re: OT: FTP speed

#7

Re: So what Bill is trying to tell you

Glenn Madsen near San Francisco

>Well, I tested my cable modem speeds the other day, because the opportunity was easily there.

Local(ish) download speed - 10Mbps+

Local(ish) upload speed - 600kbps

Across country download speed - 8Mbps+

Across country upload speed - 350kbps

Some services are move asymmetrical than others.

There are good reasons that some businesses select symmetric data links, and pay business rates for them. Fast file transfer isn't usually one of them, but it could be, in the right circumstances.

Re: OT: FTP speed

#8

Re: OT: FTP speed

Bob Fawcett

>One other thing that may get in your way is latency.

You didn't say how far apart your offices are. If your transfer is across the country, ping times will be around 60ms or higher. This long delay for round trip can affect your transfer. Most PCs have TCP/IP settings that are good for LAN but may not be for WAN.

Re: OT: FTP speed

#9

What Exactly is the Problem?

Robert Hutchins

>If you are sending individual graphics files - not video streams - why does it matter how fast they get there? Is someone waiting at the receiving end to do something to them that's time critical? If not, just set the FTP to run in a window and move on to something else to occupy your time. If there is a need for immediacy, you should look into a network backbone between your sites instead of using the 'Net. Another thing to consider is to use Unix/Linux and one its file transfer protocols, such as slip. Unix was built as a telecommunications OS and built by real software engineers, not nerdy punks like the gang that built microrot who don't seem to give an hoot nor a holler about the finer details of things. It generally does a better job at telecommnications than does winddoze.

RH - Retired from IT after 40 years; built my first network in '72.

Re: OT: FTP speed

#10

Re: OT: FTP speed

Orinda Dan

>Hi Bob,

Thanks for the info. We have 6 offices and the farthest two are around 80 miles apart, most are within a 30 mile radius of our central office. Does this distance make much of a difference in transfer speed?

Dan

Re: OT: FTP speed

#11

Re: the problem is... and thanks to all!

Orinda Dan

>Hi Robert,

We actually do need to act on the images fairly quickly once they are transferred, so speed is important. We began to use FTP to transfer voice files between offices to our transcriptionalists, and since the voice files are relatively small, speed was not a major issue. This system has since evolved to include sets of images which are large and someone on the other end needs to interpret them after the transfer.

I hear you regarding Unix. I used to work for a computer consultant while I was in college designing Informix databases on Unix boxes. I even wrote simple C programs and shell script and really enjoyed that experience. I use a Mac and occasionally dabble in the underlying Unix shell, but not long enough to do any real damage to my system. My career path took a totally different turn after college and the fine points of networking is over my head.

From all the great advice that have been posted on this topic, I think the culprit is the slow upload speed of our DSL service. I will ask our IT guys on Monday regarding this issue and pass on all the advice that you good people have provided. They will be knocked out by my sudden insight to their world so please don't spill the beans!

Dan

Re: OT: FTP speed

#12

Re: So what Bill is trying to tell you

Orinda Dan

>Hi Glenn,

That is a huge difference between upload and download speeds! I think this must be the culprit as you and others have indicated.

As an aside, it sounds like you are in my neck of the woods. Are you by chance in the East Bay? I am trying to find a good contractor here to help me build a storage shed to store lumber I had harvested after a major storm knocked down many prime trees while I was residing in the Midwest. I am currently storing them in a paid storage facility and whatever bargain there was in obtaining the lumber is quickly lost to the the storage facility.

Dan

Re: OT: FTP speed

#13

Re: OT: FTP speed

Bill Howatt

>If you are using a regular internet connection the actual connection can be very direct or go for hundreds of miles just depending on existing traffic and routing parameters when you make the connection.

Where I used to work they used to transfer large amounts of data and paid for dedicated connections - I know this wasn't cheap.

Bill

Re: OT: FTP speed

#14

Re: OT: FTP speed

Bob Fawcett

>Dan,

80 miles will not have a huge impact.

In your case DSL speed is your problem, particularly the ADSL nature of it. As others said above upload speed is usually 1/6 or less of download speed.

Check with your privider. Some DSL providers have different levels of service available at different price points. You also may want to look into a T1/DS1 type circuit. You get the same speed both directions with this.

If you are doing your transfers across the Internet, FTP has no security of its own. There is a secure version that was mentioned earlier.

If your files get very large, it is actually faster to Fedex a CD/DVD. You reach a point where a circuit with enough bandwidth is prohibitively expensive.

You can estimate transfer time file size x 10 divided by circuit speed = seconds to transfer. This assumes you get all the bandwidth of the circuit for the duration of the transfer.

Re: OT: FTP speed

#15

Think that's bad...

Mark Goodall - ATL - tooljunkie

>Oh, the cable companies and telecom's should be shot for this one......

Around here you could have a T1 with download (surfing) at 1500 and upload (office to internet) at 1500, or you could have cheaper (residential) DSL with download 1500 and upload 300, which is fine for most residentail because you download 95% of the time and upload 5% of the time.

Then cable and DSl compaines started offering 3000 and 6000 speeds.... DOWNLOAD speeds... with 200-300 upload speeds.... agian mostly for residentail who rarely upload, except when sending emails and speed isn't so imporatant for that.

Imagine the shock when businesses (accidentally) go from a T1 to a new "super-speed" cable/DSL that is supposed to be 4 times faster and then learn that it IS 4 times faster download speed, but 4 times SLOWER upload speeds than they had before.

Or vice versa, they go from 6000 download speeds with cable to 1500 with a T1.

These d*mn ISP/telecom salesmen are really good at explaining to potential customers the benefits but NEVER tell them the negative. So then the company that was just bamboozled by the ISP/telecom company thinks they have problems and ask for help. They then get referred to me by one of my clients and I start asking them questions. And then have to be the one to tell them the bad news.

Happy Woodworking!

Re: OT: FTP speed

#16

Question for you

Dan Donaldson

>If I run speed tests, I usually run around 6 to 8 meg download speed, but it plateaus at about 360k for upload. My FTP program is set up to either break a big file into parts (if the recieving server supports it) or send multiple files by opening up to 10 connections to the server. When it does this, is the effective upload speed faster than the 360K? In other words, is the upload speed for each connection or for the total. Also wondering because I have two computers sharing the connection to the cable modem through a router. If both were uploading at the same time, would it throttle so that the total of both is the 360K?

Re: OT: FTP speed

#17

Re: Question for you

wilbur

>I've tried this before as an attempt to get around upload speed caps. Basically, it doesn't work. The ISP sets a cap on the TOTAL upload bandwidth, so your 10 upload FTP connections will run at about 1/10 of your fastest upload speed each.

Re: OT: FTP speed

#18

Re: Think that's bad...

Orinda Dan

>What is the reason why DSL/cable have such a huge disparity between upload and download speeds? Is it purely economical to take advantage of the fact most people do not upload as much download, or is there a technical reason? Also, why does T1 not have this limitation and why is T1 so expensive compared to DSL/cable since it may even be slower than DSL/cable for downloads?

I swear, I learn more on this site than any where else on the internet, and I am not just referring to woodworking!

Dan

Re: OT: FTP speed

#19

360K total

Mark Goodall - ATL - tooljunkie

>You are limited by your Cable at 6000 down and 360 up.

Splitting and/or multi-thread data transfer are not designed to overcome YOUR limitations, but to defeat throttles that may be set on the other side.

If you are downloading at 6000 and the server will only download at 500 (in a multi-user server enviroment, where there may be 10 users downloading from the server at the same time) you could conceivably get multiple concurrent downloads going, let's say 4, to get it coming at 2000.

In your case with your FTP uploads at 360K, it would transfer at 360K and if you split it into two concurrent uploads, each would transfer at 180K.

This is a bit of an oversimplification, but describes it generally.

Happy Woodworking!