From: Andrew Morton <akpm@zip.com.au>
To: Radivoje Todorovic <radivojet@jaspur.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NETWORK MODULE PERFORMANCE]: How to measure it?
Date: Thu, 25 Oct 2001 10:31:34 -0700 [thread overview]
Message-ID: <3BD84C76.9A7DE8CA@zip.com.au> (raw)
In-Reply-To: <BOEOJGNGENIJJMAOLHHCEEIKCEAA.radivojet@jaspur.com>
Radivoje Todorovic wrote:
>
> Hello,
>
> I am confronted with somewhat hard problem. Say one develops Network Module
> X, i.e. using Netfilter hooks. X will (simply) mangle the packets and then
> forward them or do whatever. How can I measure the performance of X module?
> I am not sure exactly what I am asking but say, I have a Linux router with X
> module running and I need to get information what is the CPU usage under
> heavy traffic with, and without X module. Actually it would be nice to see
> the latency per-packet that X introduces and how it changes if the volume of
> traffic increases.
>
The most precise tool known to mankind is cyclesoak :)
It's at http://www.uow.edu.au/~andrewm/linux/#zc and there's
a README in the tarball.
cyclesoak measures subtractively - rather than measuring the
load of your software, it measures how much other system
load slows it down. For networking it gives results which
are repeatable down to about 0.2% of system capacity. So
you should run a known workload both with and without your
netfilter code and record the difference in cyclesoak output.
Currently it tries to lump memory bandwidth load and CPU cycle
load into a single metric, which doesn't work very well - these
things are orthogonal and should be reported separately. That's
on my TTD list.
-
prev parent reply other threads:[~2001-10-25 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 17:02 [NETWORK MODULE PERFORMANCE]: How to measure it? Radivoje Todorovic
2001-10-25 17:31 ` Andrew Morton [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=3BD84C76.9A7DE8CA@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=radivojet@jaspur.com \
/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