Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB: quantum vs. burst
Date: Thu, 16 Jan 2003 19:05:24 +0000	[thread overview]
Message-ID: <marc-lartc-104274399614988@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104272413214891@msgid-missing>

> Stef,
>
> thanks for your answer.  I've read your FAQ and other sections of
> www.docum.org. I've also been perusing Martin's original HTB
> documentation now for a couple of days and doing graphing experiments
> aimed at gaining better understanding of HTB's bursting behavior but
> some questions remain. ;)
>
> From what you write, I would still say that burst and quantum do have
> something in common, namely that they both somewhat determine how much
> data is a class permitted to send where it's its turn to send.  In your
> example, it seems to me that setting burst kind of overrides for a
> moment the behavior otherwise determined by quantum.  But I agree this
> connection between quantum and burst may be seen as too weak or abstract
> so I won't push this point any further.
>
> Important notes to take:
>
> - you use bytes *per second* to specify burst - do you mean it, or is
>   that a typo?  From docs I understand that burst is specified in bytes.
Indeed, it's in bytes.

> - more importantly, it follows from my measurements that setting burst
>   (not cburst, that's a different story) *won't* let a class go above
>   its ceil - if you are interested, go to http://kostra.uh.cz/htb-bursting/
>   (ignore the Czech text ;) and see the section under header "Experiment
> 1". Check out the complete config script and graphs of all three classes
> below.  1:78 has a bit fat burst set, still it cannot break its ceil.
> (However, it *does* make its parent class to break its ceil.)  Did I mess
> up the config?
No.  I did some tests my self witb burst and cburst.  The problem is that it's 
very difficult to measuer and explain it.  You have to believe Devik that it 
works :)  And burst is not made for big bursts like you did.  
It also helps if you disable HTB_HYSTERESIS in the htb qdisc.  See faq page 
for more info.

> - back to your example - I'd even dare to say that the class you
>   described wouldn't profit from setting burst at all *unless* there's
>   another class competing for the bandwidth.  (If there is a contention,
>   the burst setting will matter.)  Can you confirm this?
No.  If you have a 10kbyte/s link and you have a class with ceil = rate = 
5kbyte/s and a big burst/cburst (100.000byte or so), you can measure the 
burst.  The first 100.000 byte will be sended by the burst so it will be 
sended in 10 second.

I have some very detailed information about how the burst and cburst from 
parent and child classes are interacting, but I still have to create a page 
for it.  It also explains how burst and cburst can exists and how the tokens 
and ctokens are changing when you are using the burst.  Maybe something I can 
do tonight.  I will keep you informed.


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/

  parent reply	other threads:[~2003-01-16 19:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 13:34 [LARTC] HTB: quantum vs. burst Pavel Mores
2003-01-16 17:56 ` Stef Coene
2003-01-16 18:50 ` Pavel Mores
2003-01-16 19:05 ` Stef Coene [this message]
2003-01-16 19:48 ` Pavel Mores
2003-01-16 20:28 ` Stef Coene
2003-01-17 12:25 ` Pavel Mores
2003-01-18 14:20 ` Stef Coene

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=marc-lartc-104274399614988@msgid-missing \
    --to=stef.coene@docum.org \
    --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