Re: question about --bwlimit=

2004-05-26 Thread Paul Slootman
On Mon 24 May 2004, Wayne Davison wrote: output. Finally, I applied a modified version of the patch that Paul just reminded us that Debian is using, though I decided to limit the write size to bwlimit * 512 rather than bwlimit * 100 (at least for now, but feel free to argue that a different

Re: question about --bwlimit=

2004-05-24 Thread Paul Slootman
On Fri 21 May 2004, Wallace Matthews wrote: Since --bwlimit depends upon sleep(1 second), I repeated the experiment with a file that was 383 Megabyte so that when I am running unthrottled it takes significantly longer than a second (ie. ~50 seconds) to complete. I get the same bi-modal

Re: question about --bwlimit=

2004-05-24 Thread Wayne Davison
On Fri, May 21, 2004 at 02:48:12PM -0400, Wallace Matthews wrote: I can repeat this time after time. If --bwlimit is 4000 (ie. 4005, 4025, 4050,5000,7500,1,10) real is in the same range as 4001. If --bwlimit is 4000 or under (ie. 3725, 2000, 1000, 100) real is in the same range as

Re: question about --bwlimit=

2004-05-24 Thread Wayne Davison
On Mon, May 24, 2004 at 01:54:42PM -0700, Wayne Davison wrote: I'm looking into some of the old bwlimit patches to see about improving this. Here's a potential patch to make --bwlimit better. This started with Roger's idea on accumulating delay until we have enough to make a sleep call without

question about --bwlimit=

2004-05-21 Thread Wallace Matthews
I am doing some benchmarking of rsync. I am using the --bwlimit= option to throttle down rsync to predict its operation over slow communications links. I am using rsync 2.6.2 from the release site without any patches. I downloaded the release rather than pull from the CVS tree. I have 2

re: question about --bwlimit=

2004-05-21 Thread Wallace Matthews
Since --bwlimit depends upon sleep(1 second), I repeated the experiment with a file that was 383 Megabyte so that when I am running unthrottled it takes significantly longer than a second (ie. ~50 seconds) to complete. I get the same bi-modal behavior but with different values for 4000 and 4001