From: milian.wolff@kdab.com (Milian Wolff)
Subject: [lttng-dev] LTTng user-space callstacks
Date: Fri, 27 Mar 2020 18:18:09 +0100 [thread overview]
Message-ID: <2063300.72vocr9iq0@agathebauer> (raw)
In-Reply-To: <570185028.14544.1585317308324.JavaMail.zimbra@efficios.com>
On Freitag, 27. M?rz 2020 14:55:08 CET Mathieu Desnoyers wrote:
> Last time I checked, the main issue with perf's handling of cases that lack
> frame pointers is that they grab a ~2-4kB worth of stack data into the
> trace, and then post-process it with libunwind. This might be OK for
> sampling use-cases, but is not something I consider appropriate for tracing
> due to considerably increased use of tracing throughput.
>
> Has the situation changed on the perf side ?
Perf still does this. But heaptrack, of which I'm the main author, uses
libunwind to unwind on every heap allocation and it's plenty fast. Obviously
the impact is measureable and it's far away from even close to zero overhead.
But it's super useful. I guess having that capability in LTTng would be
similarly useful and if it's documented to have an overhead people can use it
with care.
Cheers
--
Milian Wolff | milian.wolff at kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3826 bytes
Desc: not available
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200327/11c0a467/attachment.bin>
prev parent reply other threads:[~2020-03-27 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 17:39 Valentin Grigorev
2020-03-26 19:41 ` Mathieu Desnoyers
2020-03-26 20:52 ` Milian Wolff
2020-03-27 13:44 ` Valentin Grigorev
2020-03-27 13:55 ` Mathieu Desnoyers
2020-03-27 15:05 ` Valentin Grigorev
2020-03-27 17:18 ` Milian Wolff [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=2063300.72vocr9iq0@agathebauer \
--to=milian.wolff@kdab.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