All of lore.kernel.org
 help / color / mirror / Atom feed
From: pljosh <witek876@interia.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB is nor fair when 'borrowing?  Can someone correct me or maybe
Date: Thu, 17 Jun 2004 21:59:21 +0000	[thread overview]
Message-ID: <40D21439.7000702@interia.pl> (raw)

Hello there!
Yesterday I started my experiments with HTB.
I configured it this way:
1: root HTB qdisc
      |
1:1 HTB class  rate 1000kbit
      |
  /-------+------\
1:40   1:50   1:60
user1  user2  user3

rate 333 & ceil 1000 for everyone.

User2 is disconnected and user1 and user3 are downloading.
For all the time (t1-t5) there are ONLY these two users downloading!

HTB should give fifty-fifty to U1 and U3... but it is not...
What is happening is that HTB gives about 350-380kbit for user3 and 
everything else(more than 600kbit) for user1... this period is marked as 
"t1" on my graph...

Tahe a look at this:
http://www.icpnet.pl/~eniu/mgr/10170_600.png
(Y-axis shows bytes/s)

During my research I found that the more classes i create (each with 
rate\x1000/no_of_users and ceil\x1000) the more precise HTB is... When you 
look at my graph - in "t1" there were 3 classes (1:40, 1:50, 1:60). Then 
I was relaunching my script with higher amount of classes - in "t2" 
there were 4 classes:rate%0/ceil\x1000 in "t3" I prepared 5 classes and 
finally in "t4" there were 6 or 7 classes.

But even in "t4" htb is not 100% fair (but it is acceptable).
In "t5" i created only two classes 1:40 and 1:60 - and then HTB is 
perfect! It is so precise you can see only one line - blue as the red 
one is behind it...

For me it looks like HTB is very good when it doesnt have to borrow from 
other classes for more than one class. When two classes are fighting for 
BW abowe "rate" then HTB is not fair...

BUT MAYBE I configured something not the way it should be and this is 
why I have what you can see...??

-josh

p.s.
I've uploaded the contents of my script's output for each of the periods 
so you can see how it was configured at each time.
The script itself is also available.
I am running debian sarge with 2.4.26.
User1 has 192.168.3.4
User2 has 192.168.3.6

http://www.icpnet.pl/~eniu/mgr/t1
http://www.icpnet.pl/~eniu/mgr/t2
http://www.icpnet.pl/~eniu/mgr/t3
http://www.icpnet.pl/~eniu/mgr/t4
http://www.icpnet.pl/~eniu/mgr/t5

http://www.icpnet.pl/~eniu/mgr/rc.shape

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-06-17 21:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 21:59 pljosh [this message]
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
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=40D21439.7000702@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 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.