Re: Problem while using HTB bandwidth limitation

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi there Nimit,

 : >>Can there be any problem if I set 10 classes each restricted to 24kbit
 : >>under a class which has been restricted to 128Kbit.
 : >>
 : >>My point is what happens if total of child classes, is more than the
 : >>parent class itself. Does it distribute fairly ie equally to all 10
 : >>classes or will there be a problem.
 : >
 : > Each class should be able to het 1/10 of 128kbit.  But it can be bursty.
 :
 : It can burst to some extent but I could see the rate going more than
 : double in some cases why is it so?

In HTB, all shaping happens in the leaf classes.  For ease on the CPU (and
apparently, the difficulty of the algorithm), HTB is designed to believe
you when you say that each of your 10 leaf classes should get 24kbit, and
it does not check the parent class to make sure the parent class is
throttling all of the children.

You had used a 24kbit rate and no specified ceiling on each of these 10
classes.  This means that you have the equivalent of 24kbit rate and
24kbit ceil.  You are guaranteeing 24kbit at all times to every class!
You might end up sending up to 240kbit (not accounting for your burst
setting either).

In order to approach better your 192kbit line with 10 classes, I would
recommend trying a configuration more like this.  Use a rate 16kbit and
ceil 24kbit for each of your classes.  This means that a leaf class will
consult the parent class for leftover bandwidth above 16kbit.  And above
24kbit, it will cease asking the parent to borrow bandwidth.

This means that all of your classes would send a maximum of 160kbit of
guaranteed traffic before consulting the parent class which has a
bandwidth to divide amongst the children.

 : Yes, now I have removed the burst parameter but can you explain me why
 : to limit all bandwidth to 188 when I have 192, I am having DSL
 : connection.

It is immaterial what sort of connection (speed) you have.  The key (and
secret) is that you must be the bottleneck.  In order for you to control
latency and bandwidth use, you must ensure that you are the slowest point.
Annoyingly, the only successful way to identify exactly what speed to use
as a bandwidth cap is experimentation.  A good general suggestion is to
lop off a couple of kbit and try capping your bandwidth exactly as Stef
suggests.  Try using 188kbit, and see if your apparent control increases.

Best of luck,

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@xxxxxxxxxxxxxx

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

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux