From: David DeLauro <daved@saintjoe.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] tc htb stats
Date: Tue, 04 Feb 2003 16:10:53 +0000 [thread overview]
Message-ID: <marc-lartc-104437510812943@msgid-missing> (raw)
I have an htb qdisc setup and it is shaping my traffic wonderfully but
I've just recently started taking a look at the output from the command
tc -s class ls dev eth?
Looking at the "rate" line I thought to myself..."cool I can use this to
graph throughput avg.es without having to worry about the "Sent bytes"
rolling over or being lost when the htb qdisc is recreated" _BUT_ it
seems the rates are inaccurate. When I look at the rate my cisco router
reports for a 5min avg and I look at a calculated 5min average (30 polls
of the tc once every 10sec) for tc they are very different. The cisco is
reported as ~2090kb/s and tc reports my parent as ~251kb/s. Even if I
take all the classes separately and add the averages together I get closer
but not that much closer. Is my math wrong? How does the tc/htb qdisc
figure the avg. rate?
--
David DeLauro
Talk sense to a fool and he calls you foolish. - Euripides
Those who do not think about their own sins make up for it by thinking incessantly about the sins of others. - C. S. Lewis (God in the Dock, "Miserable Offenders," p. 124)
Never undertake anything for which you wouldn't have the courage to ask the blessing of heaven. - G. C. Lichtenberg (1742-1799)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-02-04 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 16:10 David DeLauro [this message]
2003-02-04 16:20 ` [LARTC] tc htb stats Martin A. Brown
2003-02-04 16:30 ` David DeLauro
2003-02-04 16:37 ` 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-104437510812943@msgid-missing \
--to=daved@saintjoe.edu \
--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