From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: "Yitschak, Yehuda" <yehuday@amazon.com>,
"Mousa, Anas" <anasmous@amazon.com>,
"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Profiling LTTng tracepoint latency on different arm platforms
Date: Wed, 21 Jun 2023 09:47:19 -0400 [thread overview]
Message-ID: <fb397173-040c-9370-c6c7-3c7b1535becb@efficios.com> (raw)
In-Reply-To: <bb2ccac8e296450c96d0863937fc8db8@amazon.com>
On 6/21/23 01:39, Yitschak, Yehuda wrote:
>> On 6/20/23 10:20, Mathieu Desnoyers via lttng-dev wrote:
>>> On 6/20/23 06:27, Mousa, Anas via lttng-dev wrote:
>>>> Hello,
>>>
>>>>
>>>>
>> Arethereanysuggestionstorootcausethehighlatencyandpotentiallyimproveito
>> n*platform****1*?
>>>>
>>>> Thanks and best regards,
>>>>
>>>> Anas.
>>>>
>>>
>>> I recommend using "perf" when tracing with the sample program in a
>>> loop to figure out the hot spots. With that information on the "fast"
>>> and "slow" system, we might be able to figure out what differs.
>>>
>>> Also, comparing the kernel configurations of the two systems can help.
>>> Also comparing the glibc versions of the two systems would be relevant.
>>>
>>
>> Also make sure you benchmark the lttng "snapshot" mode [1] to make sure
>> you don't run into a situation where the disk/network I/O throughput cannot
>> cope with the generated event throughput, thus causing the ring buffer to
>> discard events. This would therefore "speed up" tracing from the application
>> perspective because discarding an event is faster than writing it to a ring
>> buffer.
>
> You mean we should avoid the "discard" loss mode and use "overwrite" loss mode since discard mode can fake fast performance ?
Yes. In addition to use "overwrite-when-buffer-full" mode, the
"snapshot" session also ensures that no consumer daemon extracts the
trace data (unless an explicit snapshot record is performed), which
allows comparing the ring buffer producer performance with minimal noise.
If you really want to benchmark the discard-when-buffer-full mode and
the the consumer daemon I/O behavior, then you need to take into account
event discarded counts and the actual trace data size that was written
to disk.
Thanks,
Mathieu
>
>>
>> Thanks,
>>
>> Mathieu
>>
>> [1] https://lttng.org/docs/v2.13/#doc-taking-a-snapshot
>>
>>> Thanks,
>>>
>>> Mathieu
>>>
>>>
>>
>> --
>> Mathieu Desnoyers
>> EfficiOS Inc.
>> https://www.efficios.com
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev@lists.lttng.org
>> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2023-06-21 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 10:27 Mousa, Anas via lttng-dev
2023-06-20 14:20 ` Mathieu Desnoyers via lttng-dev
2023-06-20 18:03 ` Mathieu Desnoyers via lttng-dev
2023-06-21 5:39 ` Yitschak, Yehuda via lttng-dev
2023-06-21 13:47 ` Mathieu Desnoyers via lttng-dev [this message]
2023-06-21 14:21 ` Yitschak, Yehuda via lttng-dev
2023-09-10 14:18 ` Mousa, Anas via lttng-dev
2023-09-11 15:52 ` Mathieu Desnoyers via lttng-dev
2023-09-11 16:20 ` Michel Dagenais via lttng-dev
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=fb397173-040c-9370-c6c7-3c7b1535becb@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=anasmous@amazon.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=yehuday@amazon.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