From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org
Cc: mbligh@google.com
Subject: LTTng 0.108 provides many performance improvements
Date: Fri, 13 Mar 2009 19:28:11 -0400 [thread overview]
Message-ID: <20090313232811.GA18251@Krystal> (raw)
Hi,
I just released LTTng 0.108. Time had come to do a bit of performance
tuning using oprofile.
Basically, the tbench workload, under flight recorder tracing, passed
from a 52 % slowdown with previous lttng to a 32 % slowdown with lttng
0.108 on my test machine (8-cores x86_64, 16GB ram).
Modifications done :
- inlined fast paths. Modularity is now provided by the build system,
not by callbacks anymore. Selecting between lockless and locked buffer
management must be done at compile-time. I'd like to keep the
"transport" around because it will be used eventually to specify where
the information must be sent rather than selecting the buffer management
mechanism (e.g. sent to physical pages (contiguous or non-contiguous),
video card memory...). The "transport" option is still there, but it
currently does not do much. The slow paths are now done in function
calls.
- Fixed false sharing problem. It looks like the kzalloc_node()
allocator, used to allocate the commit counters, does not align the
memory allocated on cache lines.
Therefore I think the new code will be _much_ easier to optimize,
because the fastpaths are very well identified and much smaller than
they were before. I diminished the tracer stack space used, register
usage and instruction cache usage.
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2009-03-13 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 23:28 Mathieu Desnoyers [this message]
2009-03-14 16:26 ` [ltt-dev] LTTng 0.108 provides many performance improvements Mathieu Desnoyers
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=20090313232811.GA18251@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mbligh@google.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