From: pljosh <witek876@interia.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB is nor fair when 'borrowing? *bug* in HTB or some
Date: Fri, 18 Jun 2004 18:45:25 +0000 [thread overview]
Message-ID: <40D33845.6020602@interia.pl> (raw)
In-Reply-To: <40D21439.7000702@interia.pl>
> I just tested with my script and also see a 5-8% advantage for the lower
> handle class.
>
> I wouldn't call it a bug though - HTB is written for high traffic setups
> and trade off needs to be made between perfect behaviour and CPU usage
> and you say it gets better with more classes.
>
> Andy.
Well - you had 5-8% while I noticed 50-80% difference! (user1 ~76kB/s
and user3 ~45kB/s).
Of course - as you can see on the graph I created: with more classes
difference beteween u1&u3 is smaller...
Can you send me the script you used for your test which gave you only
5-8%? Maybe there is something wrong with the one of mine?
-josh
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-18 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 21:59 [LARTC] HTB is nor fair when 'borrowing? Can someone correct me or maybe pljosh
2004-06-18 8:05 ` [LARTC] HTB is nor fair when 'borrowing? Can someone correct Ed Wildgoose
2004-06-18 11:05 ` [LARTC] HTB is nor fair when 'borrowing? *bug* in HTB or some pljosh
2004-06-18 11:28 ` Ed Wildgoose
2004-06-18 12:50 ` Ed Wildgoose
2004-06-18 13:30 ` pljosh
2004-06-18 18:10 ` Andy Furniss
2004-06-18 18:45 ` pljosh [this message]
2004-06-18 21:11 ` Andy Furniss
2004-06-18 21:57 ` Andy Furniss
2004-06-19 4:05 ` pljosh
2004-06-19 4:14 ` pljosh
2004-06-20 11:10 ` Andy Furniss
2004-06-20 11:56 ` pljosh
2004-06-20 13:12 ` Andy Furniss
2004-06-20 13:18 ` Ed Wildgoose
2004-06-20 15:06 ` Andy Furniss
2004-06-20 16:02 ` [LARTC] HTB is nor fair when 'borrowing? *bug* confirmed? pljosh
2004-06-24 9:38 ` Andy Furniss
2004-06-25 3:58 ` pljosh
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=40D33845.6020602@interia.pl \
--to=witek876@interia.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox