All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Boreham" <david_list@boreham.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] measure cpu load ?
Date: Tue, 01 Apr 2003 14:08:07 +0000	[thread overview]
Message-ID: <marc-lartc-104920578727137@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104918428404772@msgid-missing>

> I would like to measure the CPU load for some queuing discipline, and only
> queuing discipline. Is there any tool witch this can be done.

I think you will need to do this indirectly.

Perform an experiment like this:

Setup a test machine. It runs nothing but traffic management.

Push test traffic through the machine.

Observe the machine's CPU load.

You can now derive the relationship between traffic level,
traffic mix, traffic type and CPU load, by repeating the experiment
with different input variables.




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-04-01 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01  6:32 [LARTC] measure cpu load ? Lars Landmark
2003-04-01 14:08 ` David Boreham [this message]
2003-04-25  6:30 ` Srikanth
2003-04-25  7:30 ` Martin Devera

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-104920578727137@msgid-missing \
    --to=david_list@boreham.org \
    --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.