Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: rostedt@goodmis.org (Steven Rostedt)
Subject: [ltt-dev] Benchmarks of kernel tracing options 2 (ftrace, lttng and perf)
Date: Wed, 17 Nov 2010 18:33:02 -0500	[thread overview]
Message-ID: <1290036782.30543.84.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <AANLkTim9f2aNAaF8YgbOH3xKY9pjAtkHOoYVTv+XOE8W@mail.gmail.com>

On Wed, 2010-11-17 at 15:22 -0800, David Sharp wrote:
> On Wed, Nov 17, 2010 at 2:56 PM, Douglas Santos
> <douglas.santos at polymtl.ca> wrote:
> > Quoting Steven Rostedt <rostedt at goodmis.org>:
> >> On Wed, 2010-11-17 at 16:31 -0500, Douglas Santos wrote:
> >> > Hi all,
> >> >
> >> > This is a response to a benchmark, submitted a few weeks ago, comparing
> >> kernel
> >> > tracing options.
> >> > http://lkml.org/lkml/2010/10/28/422
> >> >
> >> > We followed the methodology described in the link bellow,
> >> > but using the shellscripts posted there to reproduce autotest scripts.
> >> > http://lkml.org/lkml/2010/10/28/261
> >> >
> >> > We disabled the extra syscall tracing on lttng, for a fair comparison.
> >> > http://lkml.org/lkml/2010/10/28/290
> >> >
> >> > Average results with tracing "on":
> >> >
> >> > lttng:  220 ns
> >> > ftrace: 260 ns
> >>
> >> Heh, so ftrace got worse with the new kernel?
> 
> Steve, can you explain how you're drawing that conclusion? Did Douglas
> run this benchmark before on a previous kernel (I didn't see it if
> so)?

Oops, no, I was thinking that this was from your tests. I remember
asking you to try the new kernel. I think I got you and Douglas
confused :-)

-- Steve





      reply	other threads:[~2010-11-17 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 21:31 Douglas Santos
2010-11-17 21:41 ` Steven Rostedt
2010-11-17 22:56   ` Douglas Santos
2010-11-17 23:22     ` David Sharp
2010-11-17 23:33       ` Steven Rostedt [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=1290036782.30543.84.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox