Thanks for the tip.
I was thinking about my suggestion, and I'm guessing that the --bwlimit feature is
implemented as
an if statement like:
if (data sent/time since last check > bwlimit) then sleep
There probably isn't a network buffer that is being checked. Maybe this can be
changed to:
On Wed, Jan 15, 2003 at 06:47:09PM -0600, Seann Herdejurgen wrote:
> rsync is optimized to conserve network resources,
> sometimes at the expense of CPU resources. As long as
> CPU's are fast and networks are slow, rsync with
> compression does a great job. However, if I run rsync on
> a slow box
rsync is optimized to conserve network resources, sometimes at the expense of CPU
resources. As
long as CPU's are fast and networks are slow, rsync with compression
does a great job. However, if I run rsync on a slow box (166MHz Ultra SPARC) over a
fast network
(100Mb/s), the compression kills
