On Sat, Dec 16, 2000 at 01:34:29AM -0600, Brian Minton wrote:
> On Fri, Dec 15, 2000 at 03:28:51PM -0700, Charles Curley wrote:
> > Normally I would compress on the originating machine, to minimize traffic
> > over the net, always a major consideration. However, if the originating
> > machine is an older, slower machine, it may be considerably faster to
> > compress on the target.
>
> It might be best to use ssh -C then (zlib compression of the ssh stream
> itself) although I don't think you would want to do that in conjunction with
> compressing(bzip2 or gzip) on the originating machine
Hmmm, not necessarily. If I'm compressing on the target machine because it
is faster to do that than compress on the originating machine, then I
don't think I want to slow down the originating machine with compression
at the SSH level.
The decompression at the other end would also slow down the target,
although in this example not as much. Methinks if the intent is to collect
a bunch of data, and store it compressed on some other computer, then only
compress it once.
But absent a bunch of testing on the actual hardware, it's a judgement call.
--
-- C^2
No windows were crashed in the making of this email.
Looking for fine software and/or web pages?
http://w3.trib.com/~ccurley
PGP signature
