From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwidth Control Tolerances
Date: Wed, 07 Jan 2004 17:36:56 +0000 [thread overview]
Message-ID: <200401071836.56689.stef.coene@docum.org> (raw)
In-Reply-To: <002801c3d3eb$4634da30$6401a8c0@pturley>
On Tuesday 06 January 2004 19:02, Patrick Turley wrote:
> This is, of course, very valuable feedback. Unfortunately, given the
> responses I've had so far, I see that I didn't make it clear what I'm
> really looking for.
I also did some htb tests. I created scripts that uses iptables or tc
counters to log the number of bytes. And most of the time I had bursty
results. But I think this burst is more reated to the test setup:
collisions, retransmits, CPU/disk, ...
I did some burst tests and recorded the rate each 500ms:
http://docum.org/stef.coene/qos/tests/htb/burst/
I used ethloop. Ethloop can be used to simulate a htb qdisc on the lo device
(it can be found on the htb homepag). So there is no network involved, it
only records bytes like they should be sended if this was a real device. So
this is the perfect situation for htb.
And.... as you can see on the graphs, the rate is very stable and allmost
perfect accurate. So the bursts or rate deviation are not htb related.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-01-07 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 0:23 [LARTC] Bandwidth Control Tolerances Patrick Turley
2004-01-06 17:20 ` Martin A. Brown
2004-01-06 18:02 ` Patrick Turley
2004-01-06 18:02 ` Patrick Turley
2004-01-06 18:03 ` Patrick Turley
2004-01-07 17:36 ` Stef Coene [this message]
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=200401071836.56689.stef.coene@docum.org \
--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 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.