LinkBack URL
About LinkBacks
Reply With QuoteIt depends on how you're sending the files. If you're using a binary transfer such as ftp or scp, that sounds too high. If you're emailing the files, it would be just about right.
Do a google on "uuencode overhead" and ye shall be enlightened.
40% overhead for uploads I recently switched from dial-up satellite (DRS) to cable (roadrunner). I emailed some large zip files recently. I have a utility called DU Meter that tracks download/upload activity. I noticed that it reported far more bytes were being sent than could be explained by the filesize. For example, it took 6.98 MB of upload activity to send a 4.96 MB file. This represents an overhead of more than 40%!! I get similar results when sending other large files. Do the Internet protocols have this much overhead or is something else going on here?
With dial-up, I could never be sure how much retransmission was going on (due to line noise) but I wouldn't think a cable connection would have that problem...(?)
It depends on how you're sending the files. If you're using a binary transfer such as ftp or scp, that sounds too high. If you're emailing the files, it would be just about right.
Do a google on "uuencode overhead" and ye shall be enlightened.
Thanks...
I had no idea email encoding was so inefficient. Before I got cable, I had DRS (one-way) satellite... so this also explains why I was unable to get more than low-twenties of throughput with my V.90 modem (33 upstream reduced by 40% overhead).
BTW, I'm familiar with ftp, but what is scp?
40% overhead for uploads scp (secure copy) is similar to FTP, but it uses encryption derived from SSH. It has some advantages, one of them being that most versions of it support compression. Won't help you any for copying something like music or pictures, but if you're copying documents or databases, it can speed things up quite a bit.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions 
Bookmarks