From: a.aleksandrov@yadro.com (Aleksander Aleksandrov)
Subject: [lttng-dev] Babeltrace 2.0.2 performance issue
Date: Thu, 2 Apr 2020 16:30:25 +0000 [thread overview]
Message-ID: <ae52dda9bc3b4e54ba097209180e1ac9@yadro.com> (raw)
In-Reply-To: <76e78e538b804aa2b78f320510e8c10d@yadro.com>
??: Aleksander Aleksandrov
??????????: 12 ????? 2020 ?. 14:36
????: jeremie.galarneau at efficios.com
?????: simon.marchi at efficios.com; francis.deslauriers at efficios.com
????: Babeltrace 2.0.2 performance issue
Hello Jeremie,
My name is Aleksandr, I had a pleasure to write a plugin for babeltrace2 and I faced some performance issue (bt2 vs bt1).
I attached the simple LTTng user-space log which is used to show my issue. As far as I understand Babeltrace2's performance is comparable to Babeltrace1's.
* Babeltrace 2:
tag: v2.0.2
BABELTRACE_MINIMAL_LOG_LEVEL=INFO ./configure --disable-man-pages --disable-debug-info CFLAGS='-O3 -DNDEBUG -Wno-error'
LD_LIBRARY_PATH=./src/lib/.libs ./src/cli/.libs/babeltrace2 my-lttng-trace -o dummy 12,70s user 0,03s system 99% cpu 12,745 total
* Babeltrace 1:
tag: v1.5.8
./configure CFLAGS='-O3 -DNDEBUG -Wno-error'
./converter/babeltrace my-lttng-trace -o dummy 8,30s user 0,03s system 100% cpu 8,334 total
Babeltrace v2.0.2 is slower (~50%, processing time: 12,745 s vs 8,334 s) than Babeltrace v1.5.8 with a dummy output according to my measurements.
I would be happy to receive any help or clarification from you.
Thank you for your time!
Best regards,
Aleksandr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200402/2c5f0f7a/attachment.htm>
next parent reply other threads:[~2020-04-02 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <76e78e538b804aa2b78f320510e8c10d@yadro.com>
2020-04-02 16:30 ` Aleksander Aleksandrov [this message]
[not found] ` <9ee46aeb-1b9b-c7d4-94ea-c15772bc05eb@efficios.com>
[not found] ` <5f3249fe30e040b5b4a444fba495de62@yadro.com>
[not found] ` <6992879d-d139-06f5-d325-02530ad2c1b1@efficios.com>
[not found] ` <e21e3ce3-0180-7aa7-aa16-9e889b69269b@efficios.com>
2020-04-02 16:32 ` Aleksander Aleksandrov
2020-04-02 16:53 ` Jonathan Rajotte-Julien
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=ae52dda9bc3b4e54ba097209180e1ac9@yadro.com \
--to=a.aleksandrov@yadro.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