From: Martin Hunt <hunt@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Systemtap benchmarking doc draft
Date: Tue, 28 Feb 2006 20:04:00 -0000 [thread overview]
Message-ID: <1141157050.3404.13.camel@dragon> (raw)
In-Reply-To: <440369D1.6030705@redhat.com>
On Mon, 2006-02-27 at 16:06 -0500, William Cohen wrote:
> SystemTap Language micro metrics (costs of various operations):
> cost of associative array operations
transport speed (both maximum and writing to disk)
transport overhead (how much cpu time it takes)
printf overhead
probe overhead (all the stuff the translator emits for each probe)
stack dump/trace
symbolic lookup
systemtap function call overhead
systemtap string operations (things like concatenation do
many string copies and are slow)
> Kernel instrumentation limits:
> Number of probes that can be registered at a time
> Number of kretprobes active
>
> SystemTap limits:
> Maximum elements in associative array
This is a define. Probably needs to be a variable. Anyway, it is
adjustable.
> Number of actions/steps in probe.
Ditto
Martin
prev parent reply other threads:[~2006-02-28 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 21:06 William Cohen
2006-02-28 20:04 ` Martin Hunt [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=1141157050.3404.13.camel@dragon \
--to=hunt@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=wcohen@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).