From: Thomas Graf <tgraf@suug.ch>
To: Mark Seger <Mark.Seger@hp.com>
Cc: netdev@vger.kernel.org
Subject: Re: update frequency for stats in /proc/net/dev
Date: Tue, 18 Dec 2007 15:57:07 +0100 [thread overview]
Message-ID: <20071218145707.GV11220@postel.suug.ch> (raw)
In-Reply-To: <4767CD16.5050904@hp.com>
* Mark Seger <Mark.Seger@hp.com> 2007-12-18 08:37
> Anyhow, I just wanted to let people know that ALL tools that monitor
> once a second on older counters will get the wrong numbers and tools
> that correct for the wrong number by using fractional intervals (and I
> suspect mine is the only one that does) but run on newer kernels will
> also get the wrong numbers. In any event, if anyone is interested in
> trying out collectl - it monitors a LOT more than just networks - you
> can snag a copy of from http://collectl.sourceforge.net/ if you'd like
> to take if for a drive. The website has a lot of output examples to
> give you a better idea what it can do. I even included a writeup about
> the odd network performance observations at
> http://collectl.sourceforge.net/NetworkStats.html
I've solved this problem by using netlink to read the interface counters
ten times per second and maintain an own counter from which I calculate
the rate exactly once per second/minute/hour. The rate per second may
still be inaccurate to some degree, therefore I keep a history of 2-5
rates and take them into account to smoothen the result. This works
fairly well with _all_ operating systems.
next prev parent reply other threads:[~2007-12-18 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 13:37 update frequency for stats in /proc/net/dev Mark Seger
2007-12-18 14:57 ` Thomas Graf [this message]
2007-12-18 15:10 ` Mark Seger
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=20071218145707.GV11220@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=Mark.Seger@hp.com \
--cc=netdev@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.