From: Stef Coene <stafke@iname.com>
To: lartc@vger.kernel.org
Subject: [LARTC] CBQ : Bug ?
Date: Mon, 23 Apr 2001 11:00:05 +0000 [thread overview]
Message-ID: <marc-lartc-98802376215823@msgid-missing> (raw)
Hi there,
I have done a lot of testing and I have a few questions about CBQ. You
can split the traffic in diffent classes and it works great. But to do
this, I have to add as the first class a bounded class with rate available link-bandwidth.
I have tried different rates but CBQ isn't very accurate. I added the
testing results at the bottom of the posting (or go to
http://users.belgacom.net/staf/) As you can see there are some very
strange results (notice the change in throughput when I changed the rate
1kbps around 71475kbps and 135556kbps).
I also noticed that the accuracy of splitting the traffic in different
classes is very good unless you want to give a class < 25% of the
bandwidth.
I'm wondering if someone encountered the same problem and/or if it is a
problem with tc or the kernel itself.
--
Staf
More QOS info : http://users.belgacom.net/staf/
RESULTS :
RATE_TOT RESULT
1 kbps 1.05 KB/s
2 kbps 2.10 KB/s
3 kbps 3.04 KB/s
4 kbps 4.17 KB/s
5 kbps 5.02 KB/s
10 kbps 9.91 KB/s
15 kbps 14.7 KB/s
20 kbps 18.8 KB/s
30 kbps 29.2 KB/s
40 kbps 36.5 KB/s
50 kbps 49.2 KB/s
60 kbps 49.4 KB/s
65 kbps 49.3 KB/s
67 kbps 49.3 KB/s
68 kbps 49.3 KB/s
69 kbps 49.3 KB/s
71475 bps 51.1 KB/s
71476 bps 69.7 KB/s
70 kbps 69.9 KB/s
80 kbps 69.9 KB/s
90 kbps 70.3 KB/s
100 kbps 75.4 KB/s
130 kbps 75.7 KB/s
135556 bps 78.7 KB/s
135557 bps 139 KB/s
140 kbps 140 KB/s
150 kbps 140 KB/s
200 kbps 140 KB/s
300 kbps 140 KB/s
500 kbps 140 KB/s
1000 kbps 140 KB/s
1310719bps 146 KB/s
1310720bps 940 KB/s
2000 kbps 945 KB/s
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-04-23 11:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-98802376215823@msgid-missing \
--to=stafke@iname.com \
--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.