On Sun, Mar 09, 2008 at 09:34:34AM -0700, Andrew Lentvorski wrote:
[EMAIL PROTECTED] wrote:
Maybe you could use the --max_upload_rate flag when you start bittorrent?
From man bittorrent:
--max_upload_rate kbytes
maximum rate to upload at in kilobytes, 0 means no
limit
(default 0)
You can, but that doesn't really do what you want either. You'd ideally
like to blast out a couple of seeds and then throttle way back.
I certainly don't want to do that. If I saturate my relatively slow
uplink, my downlink suffers because responses get queued instead of being
sent. If my uplink is only partially saturated, then the downlink will
continue to work at full speed.
I _never_ want it to saturate my uplink, or my entire net connection
becomes nearly worthless. VOIP stops working and downloads are unpleasant.
I can let it dribble away at a fraction of my total uplink and hardly
notice that it is running. I suspect most home internet connections will
be like this.
My main concern is that the max_upload_rate is global, not per torrent.
David
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
