Wilson, Mark - MST [[EMAIL PROTECTED]] writes:
> The file being sent is compressed and doesn't exist at the destination at
> time of sending. Compression option is not used in rsync.
You've got a high speed, low latency link, copying a compressed file from
source to a destination where it doesn't exist?
Hmm, under those conditions, to be honest, is rsync even appropriate?
You could just copy the file with rcp/scp (heck, or even ftp). You're
not benefitting at all from rsync's algorithm.
Unless you expect to update the file later, in which case you should
leave it uncompressed or else it's not going to be an efficient later
update.
Assuming rsync though, a better comparison to your ftp would be to use
the -W option of rsync, which will just copy the file entirely and not
fiddle with the overhead of block and checksum information, nor the
time spent to compute the checksums.
-- David
/-----------------------------------------------------------------------\
\ David Bolen \ E-mail: [EMAIL PROTECTED] /
| FitLinxx, Inc. \ Phone: (203) 708-5192 |
/ 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \
\-----------------------------------------------------------------------/
