From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] new perflow rate control queue
Date: Mon, 04 Apr 2005 15:10:48 +0000 [thread overview]
Message-ID: <425158F8.4090105@dsl.pipex.com> (raw)
In-Reply-To: <20050404152117.6d90635d.lark@linux.net.cn>
Wang Jian wrote:
> Hi Andy Furniss,
>
> I just tried HTB+SFQ. I replace 'perflow ...' in t.sh with 'sfq'.
>
> The test result is very bad. The speed is not stable, and speed
> variation is too large when considering fairness.
>
> The HTB is rate€kbps,ceil€kbps. I use 7 streams to test. Streams's
> speed vary from 3.4kbps to 28.7kbps. The test last about 10 minutes, and
> the speeds don't like to converge.
>
> Maybe the fairness is achived in long run, but it hurts applications
> that need bandwidth guarantee.
Yes - I can make sfq look bad in tests, if the only difference is dst
port then it just doesn't work and if the ip addresses are sequential
it's not too good. In practice I use esfq as you can use more hash
buckets - but perturb is horrable for the packet reordering.
I think perflow is going to be far better for me - just that having low
bandwidth means I would never send interactive to sfq anyway and only
use it for bulk whose rate is controlled by htb per user and is quite
variable - so for me just letting htb do rate would be fine.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-04-04 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 7:21 [LARTC] new perflow rate control queue Wang Jian
2005-04-04 8:51 ` Patrick McHardy
2005-04-04 9:10 ` Wang Jian
2005-04-04 11:42 ` Andy Furniss
2005-04-04 13:53 ` Wang Jian
2005-04-04 14:39 ` Wang Jian
2005-04-04 15:10 ` Andy Furniss [this message]
2005-04-04 15:23 ` Andy Furniss
2005-04-04 15:57 ` Wang Jian
2005-04-05 22:40 ` Andy Furniss
2005-04-06 4:17 ` Wang Jian
2005-04-06 12:29 ` Andy Furniss
2005-04-06 12:48 ` Wang Jian
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=425158F8.4090105@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.