Everything that
blue_cowdawg says is accurate. There are really only 2 ways that you could make things appreciably faster:
- compress the file before the copy, or use a copy method that compresses as it copies
- split the file into pieces, and do the transfer in parallel (and reassemble it afterwards). In some cases, a server won't allow a single connection to use more than a pre-set transfer limit, but will allow multiple connections that can sum to more than the single max rate. As blue_cowdawg also points out, this method won't help if some intervening hop ends up being the bottleneck
With no more info than 'a server in China', it's hard to be more specific. However, given the file size, and the likely sub-optimal transfer rate, it would be wise to use something like
Net::FTPSSL, where the 'put' command allows you to pass an offset of -1, and it will attempt to resume where it left off.
fnord
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.