All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: ADSL Calculator
Date: Fri, 17 Jun 2005 13:30:18 +0000	[thread overview]
Message-ID: <42B2D06A.2080503@wildgooses.com> (raw)
In-Reply-To: <20050617011135.GA9675@yamamaya.is-a-geek.org>


>
> Bittorrent is harder to shape than most things.


I think the issue is lots of connections all going into fast start?

I liked Andy's idea of having a seperate queue for the first few Kbytes 
of new connections and pegging it with a VERY short queue length.  This 
means that connections in fast start will get a packet drop very early 
on unless they play very nicely

I guess one could do something like making it the very lowest priority 
class in a standard HTB setup with near zero guaranteed rate and then it 
would be self throttling, the first few connections can come in, mop up 
all the bandwidth, and new connections after that get packet loss very 
early on (because they only get the leftovers), forcing them to slow 
down much more quickly.

Once they have transferred some small amount of data they fall back into 
your normal traffic shaping queues and everything proceeds as normal.

I guess for an even better approach, only do this nasty trick on your 
"bulk" incoming connections...

If anyone gives this a serious test then please do report back with your 
findings

Ed W
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-06-17 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-17  1:11 [LARTC] Re: ADSL Calculator Tobias Diedrich
2005-06-17 10:15 ` Per Marker Mortensen
2005-06-17 10:45 ` Andy Furniss
2005-06-17 13:30 ` Ed W [this message]
2005-06-19 10:36 ` Andy Furniss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42B2D06A.2080503@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.