* Re: [LARTC] [LONG] Weights not working
2003-07-26 4:32 [LARTC] [LONG] Weights not working Raj Mathur
@ 2003-07-26 4:59 ` Rio Martin.
2003-07-26 6:21 ` Raj Mathur
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Rio Martin. @ 2003-07-26 4:59 UTC (permalink / raw)
To: lartc
On Saturday 26 July 2003 11:20, Raj Mathur wrote:
> Hi,
> The Description
> ---------------
> Am making a package for a VSAT ISP. Running Red Hat 8.0 with the
> updated kernel (2.4.20) and patched for HTB on the bandwidth
> management system (BMS). BMS has two ethernet interfaces: eth1 at
... [x]
> The Problem
> -----------
> Throttling is working fine in both directions. However, when the link
> is choked the PCs do not get bandwidth proportional to their RATEs or
> CEILs. So if all the PCs start downloading simultaneously, each pool
> gets ~85 Kbps, instead of pools (a) and (c) getting 64 Kbps each and
> (b) getting 128 Kbps.
It will be getting worse if your hosts start to open Kazaa or Download
Accelerator Pro brutally (let say 10 - 20 DAP, Kazaa, FlashGet)
As i ve seen in your script, you didnt play the Quantum value.. This is
exactly the same just like i did my HTB working for the first time..
Set the Quantum value to suits your bandwidth manager..
Regards,
Rio Martin.
--
Look, we play the Star Spangled Banner before every game. You want us
to pay income taxes, too?
-- Bill Veeck, Chicago White Sox
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [LARTC] [LONG] Weights not working
2003-07-26 4:32 [LARTC] [LONG] Weights not working Raj Mathur
2003-07-26 4:59 ` Rio Martin.
@ 2003-07-26 6:21 ` Raj Mathur
2003-07-29 5:22 ` Rio Martin.
2003-07-29 7:42 ` Stef Coene
3 siblings, 0 replies; 5+ messages in thread
From: Raj Mathur @ 2003-07-26 6:21 UTC (permalink / raw)
To: lartc
Hi Rio,
>>>>> "Rio" = Rio Martin <rio@martin.mu> writes:
>> The Problem
>> -----------
>> Throttling is working fine in both directions. However, when
>> the link is choked the PCs do not get bandwidth proportional to
>> their RATEs or CEILs. So if all the PCs start downloading
>> simultaneously, each pool gets ~85 Kbps, instead of pools (a)
>> and (c) getting 64 Kbps each and (b) getting 128 Kbps.
Rio> It will be getting worse if your hosts start to open Kazaa or
Rio> Download Accelerator Pro brutally (let say 10 - 20 DAP,
Rio> Kazaa, FlashGet)
Rio> As i ve seen in your script, you didnt play the Quantum
Rio> value.. This is exactly the same just like i did my HTB
Rio> working for the first time.. Set the Quantum value to suits
Rio> your bandwidth manager..
Hmm, so if I understand you correctly you're saying that the QUANTUM
in each SFQ should be proportional to the bandwidth allocated to that
pool. As per the documents I've read, this must also be >= the
maximum packet size.
I /could/ do that but that'd mean that I have to scan all the pools
beforehand and figure out the weights for each pool, since the weights
are relative. I was hoping that htb.init would do that for me
automatically :)
Another question: wouldn't the QUANTUM only affect the sharing within
a specific pool? Or would it have an impact at the global level
(inter-pool) bandwidth allocation too?
Regards,
-- Raju
--
Raj Mathur raju@kandalaya.org http://kandalaya.org/
GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F
It is the mind that moves
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [LARTC] [LONG] Weights not working
2003-07-26 4:32 [LARTC] [LONG] Weights not working Raj Mathur
2003-07-26 4:59 ` Rio Martin.
2003-07-26 6:21 ` Raj Mathur
@ 2003-07-29 5:22 ` Rio Martin.
2003-07-29 7:42 ` Stef Coene
3 siblings, 0 replies; 5+ messages in thread
From: Rio Martin. @ 2003-07-29 5:22 UTC (permalink / raw)
To: lartc
On Saturday 26 July 2003 13:09, Raj Mathur wrote:
> Hi Rio,
> Hmm, so if I understand you correctly you're saying that the QUANTUM
> in each SFQ should be proportional to the bandwidth allocated to that
> pool. As per the documents I've read, this must also be >= the
> maximum packet size.
Not quantum value in SFQ, but R2Q ..
Perhaps Stef have something more about this, i am just user, i am just using
this HTB without understanding about how this work more deeper ..
Regards,
Rio Martin.
--
Don't put off for tomorrow what you can do today, because if you enjoy
it today you can do it again tomorrow.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [LARTC] [LONG] Weights not working
2003-07-26 4:32 [LARTC] [LONG] Weights not working Raj Mathur
` (2 preceding siblings ...)
2003-07-29 5:22 ` Rio Martin.
@ 2003-07-29 7:42 ` Stef Coene
3 siblings, 0 replies; 5+ messages in thread
From: Stef Coene @ 2003-07-29 7:42 UTC (permalink / raw)
To: lartc
On Tuesday 29 July 2003 07:22, Rio Martin. wrote:
> On Saturday 26 July 2003 13:09, Raj Mathur wrote:
> > Hi Rio,
> > Hmm, so if I understand you correctly you're saying that the QUANTUM
> > in each SFQ should be proportional to the bandwidth allocated to that
> > pool. As per the documents I've read, this must also be >= the
> > maximum packet size.
>
> Not quantum value in SFQ, but R2Q ..
> Perhaps Stef have something more about this, i am just user, i am just
> using this HTB without understanding about how this work more deeper ..
Quantum is a number of bytes. It is calculated as rate / r2q. And r2q can be
set when you add a htb qdisc (default = 10). Quamtum is the number of bytes
that each class can send when they are fighting for remaining bandwidth.
The minimum quantum is 1500 (max packet size). So you can send at least 1
packet. The maximum is 60000 and this is hard coded in htb to prevent class
starvation. If a class has a quantum of 1000000000 it will send 1000000000
bytes before other classes are served. So to prevent this, 60000 is the
maximum.
The rate of a class is the minimum bandwidth a class will get. If all classes
are sending theire rate AND the parent has more bandwidth, each class may
send quantum bytes. So quantum is only imporant if the parent has more
bandwidth then the sum of the rate of the active child classes.
I never changed quantum in a test situation to see what's happing, but there
are reports that you can improve your setup by choosing the right quantums.
Just take quantum not too small (5000 so you can send some packets in 1
turn). But for higher rates, take a higher quantum. But don't give 2
classes 2 total different quantums like 2000 and 600000.
I hope this helps. I know what quantum does, but if you get some real
improvements if you change quantum, let me know so I can update the faq page
on docum.org.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread