how to control upload data in bittorrent clients

[RW]

On Sun, 07 Feb 2010 10:51:20 +0100
Morgan Wesström <freebsd-questions at pp.dyndns.biz> wrote:

> RW wrote:
> > On Sat, 06 Feb 2010 23:14:45 +0100
> > Morgan Wesström <freebsd-questions at pp.dyndns.biz> wrote:
> > 
> > 
> >>> 1)  in the transmission web   it showing  downloading is 10  kbps
> >>> to 30 kbps    but uploading  it shows  50 to 92 kbps my question
> >>> is  is it possible to  limit the uploading data rate , how can I
> >>> do this ?
> > 
> >> Check out Daniel Hartmeier's excellent article on how to prioritize
> >> TCP ACKs (and other traffic). It will explain what you experience
> >> and solve the problem for you.
> > 
> > It's a good idea to handle this from within  transmission too.
> > Rate limiting works best at the TCP level.
> 
> Well, the thing is that if you prioritize your TCP ACKs you won't have
> to do any rate limiting within transmission. You can then use your
> full upload and download simultaneously. Don't you want to use the
> bandwidth you pay for? :-)

You can't get the full bandwidth because you need to set the upload
limit at a level that can be sustained upstream in your router or modem;
otherwise it doesn't work properly. You can't just use your nominal
line-speed or let altq  pick-up the interface speed.

It depends what you are trying achieve. If your sole object is to
prevent ack delays reducing tcp download speed then altq will do it.
However, if you want to seed afterwards you need to reduce the impact on
latency-sensitive protocols like http and imap. Further traffic
prioritization  does help, but I find that I get better results if I
also set the client to limit itself a bit below the altq limit.

In my experience tcp limiting also produces  steadier uploads than altq
so the average rate can actually be higher.


On Sun, 7 Feb 2010 09:21:33 +0000
dhaneshk k <dhaneshkk at hotmail.com> wrote:

> how  can we control it within transmission ?  Can you shed some light
> in this  solution 

preferences --> speed