From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stef Coene Date: Wed, 07 Jan 2004 17:36:56 +0000 Subject: Re: [LARTC] Bandwidth Control Tolerances Message-Id: <200401071836.56689.stef.coene@docum.org> List-Id: References: <002801c3d3eb$4634da30$6401a8c0@pturley> In-Reply-To: <002801c3d3eb$4634da30$6401a8c0@pturley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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/