Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Cross-domain influence on overhead
Date: Mon, 7 Jan 2013 08:44:04 -0500	[thread overview]
Message-ID: <20130107134404.GA30165@Krystal> (raw)
In-Reply-To: <524C960C5DFC794E82BE548D825F05CF5BC8AEAD@EU-MBX-04.mgc.mentorg.com>

* Oestman, Fredrik (Fredrik_Oestman at mentor.com) wrote:
> Hi,
> 
> I've noticed the following somewhat puzzling effect on both Intel and
> ARM architecture computers:
> 
> If all trace events are enabled in one domain only, either kernel or
> user space, and there are lots of static tracepoints instrumented in
> the other, then these inactive tracepoints start causing overhead of
> about the same magnitude as if they were active, as if trace events
> were enabled in this domain.
> 
> Is there any obvious explanation to this behaviour?

No, this would be really surprising.

Can you provide your test script, and more details about the way you
perform your benchmarks ? How is the overhead calculated ? From how many
tracepoints hit ? How many processes spawned/exec() done ? How many
tracepoints hit per process ?

Thanks,

Mathieu

> 
> Cheers,
> 
> Fredrik ?stman
> 
> http://go.mentor.com/sourceryanalyzer/
> 
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com



  reply	other threads:[~2013-01-07 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 11:53 Oestman, Fredrik
2013-01-07 13:44 ` Mathieu Desnoyers [this message]
2013-01-07 13:53   ` Oestman, Fredrik

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=20130107134404.GA30165@Krystal \
    --to=mathieu.desnoyers@efficios.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