Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: julien.desfossez@polymtl.ca (Julien Desfossez)
Subject: [ltt-dev] LTTng-UST vs SystemTap userspace tracing benchmarks
Date: Thu, 17 Feb 2011 11:20:51 -0500	[thread overview]
Message-ID: <4D5D4AE3.4070703@polymtl.ca> (raw)
In-Reply-To: <4D5AA8F4.8060902@redhat.com>

On 02/15/2011 11:25 AM, William Cohen wrote:
> On 02/15/2011 10:53 AM, Julien Desfossez wrote:
>> LTTng-UST vs SystemTap userspace tracing benchmarks
>>
>> February 15th, 2011
>>
>> Authors: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
>>          Julien Desfossez <julien.desfossez at polymtl.ca>
> 
>> * SystemTap probe (stap testutrace.stp -F) :
>> probe process("./.libs/tracepoint_benchmark").mark("single_trace") {
>>     printf("%d : %s\n", gettimeofday_ns(), $arg1);
>> }

Hi William,
> How much of the SystemTap overhead is due to the printf() statement in the probe? What is the run time for the following:
> 
> probe process("./.libs/tracepoint_benchmark").mark("single_trace") {}
Except the fact that it produces a warning because the probe is empty,
the results differ a little but not as much as I expected. I also tested
(in flight recorder mode) with just removing the gettimeofday_ns() call
(and printing) :

# of threads   With printf    Without gtod_ns()   Without printf
1              0:58.36        0:52.27             0:46.45
2              1:49.94        1:37.61             1:27.33
4              2:38.49        2:35.13             2:50.87

> Is the code for the benchmarks available, so we can take a look at reducing the overhead of SystemTap?
For those who want to play with the benchmark, we setup a git repository
here : git://git.lttng.org/benchmarks.git

If you have any suggestions or ideas to make these tests better, we'll
be happy to integrate it.

Thanks,

Julien




  reply	other threads:[~2011-02-17 16:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 15:53 Julien Desfossez
2011-02-15 16:25 ` William Cohen
2011-02-17 16:20   ` Julien Desfossez [this message]
2011-02-15 16:26 ` Frank Ch. Eigler
2011-02-15 16:54   ` Mathieu Desnoyers
2011-02-15 17:39     ` Frank Ch. Eigler
2011-02-15 22:25       ` Mathieu Desnoyers
2011-02-15 17:00   ` Stefan Hajnoczi
2011-02-15 17:04     ` Mathieu Desnoyers
2011-02-16 10:56     ` Mark Wielaard
2011-02-16 18:50       ` Roland McGrath
2011-02-16 20:00         ` [ltt-dev] Porting "jump labels" to userspace (was: Re: LTTng-UST vs SystemTap userspace tracing benchmarks) Mathieu Desnoyers
2011-02-16 20:04           ` Roland McGrath
2011-02-16 20:17             ` [ltt-dev] Porting "jump labels" to userspace David Daney
2011-02-16 20:39               ` Mathieu Desnoyers
2011-02-16 20:45                 ` Thomas Gleixner
2011-02-16 21:42                   ` Peter Zijlstra
2011-02-17 13:58                     ` Ingo Molnar
2011-02-16 20:14           ` David Daney
2011-02-16 20:36             ` Mathieu Desnoyers
2011-02-16 20:55         ` [ltt-dev] LTTng-UST vs SystemTap userspace tracing benchmarks Stefan Hajnoczi
2011-02-16 21:05           ` Mathieu Desnoyers
2011-02-16 21:16           ` Mark Wielaard
2011-02-15 17:03 ` Mark Wielaard
2011-02-16 15:30 ` Tom Tromey
2011-02-16 18:19   ` Roland McGrath
2011-02-17 17:33   ` Julien Desfossez
2011-02-17 19:11     ` Josh Stone
2011-02-17 19:33       ` Julien Desfossez
2011-02-17 19:47         ` Josh Stone

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=4D5D4AE3.4070703@polymtl.ca \
    --to=julien.desfossez@polymtl.ca \
    /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