From: Adel Belkhiri via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] delay in Java/python events
Date: Mon, 10 Jul 2023 11:49:57 -0400 [thread overview]
Message-ID: <CAMxxxdMyENFGH+c0z-XE=TZFPNCmtAG1M2UAXBm_ET5pnq=fgQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 742 bytes --]
Hello LTTng community,
Currently, I'm tracing a java (and Python) application using LTTng. I
noticed there is a considerable delay between the time the tracepoint
instruction is executed and the time its corresponding event is recorded by
LTTng. It seems that the problem comes from the fact that LTTng uses agents
to handle java/Python events. Is there any benchmark measuring such delay?
Is it possible to minimize this delay (for example by flushing the logger)?
Currently, I'm considering putting my tracepoints in a shared library and
calling them from within Java code using JNI so that events recording will
be "synchronous" with application code execution. Is there any other
technique that I can use? Thank you for your help.
Adel
[-- Attachment #1.2: Type: text/html, Size: 798 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
reply other threads:[~2023-07-10 15:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAMxxxdMyENFGH+c0z-XE=TZFPNCmtAG1M2UAXBm_ET5pnq=fgQ@mail.gmail.com' \
--to=lttng-dev@lists.lttng.org \
--cc=adel.belkhiri@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).