From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Gour DEV <lakshyagour10@gmail.com>, lttng-dev@lists.lttng.org
Subject: Re: Memory Consumption High After Upgrading to 2.13 from 2.10
Date: Tue, 11 Mar 2025 14:55:21 -0400 [thread overview]
Message-ID: <38dab5ef-f106-4e57-9e36-b4b30015c019@efficios.com> (raw)
In-Reply-To: <8a3a094c-3afc-49da-8764-8fec1179f7c0@efficios.com>
Hi Lakshya,
On 3/11/25 12:25 PM, Gour DEV wrote:
> Hi, Kienan
>
> here is the requested output
>
> root@localhost:~# top -b -n 1 | grep lttng
> 4841 root 20 0 11.5g 11.0g 11.0g S 5.9 35.4 8:39.93
> lttng-c+
> 4824 root 20 0 1098824 26456 5380 S 0.0 0.1 0:07.25
> lttng-s+
> 4825 root 20 0 48872 2188 1012 S 0.0 0.0 0:00.00
> lttng-r+
> 4843 root 20 0 3680 1160 816 S 0.0 0.0 0:00.23
This top output for `localhost` seems very different than the output for
`localhost` in your previous message.
> lttng-r+
> root@localhost:~# nrpco
> bash: nrpco: command not found
> root@localhost:~# nproc
> 16
> root@localhost:~# cat /sys/devices/system/cpu/possible
> 0-15
>
You indicated the bookworm machine has 32 cores, this is showing 16. If
you're comparing a 16 core machine to a 32 core machine, it is very
normal that the memory usage is higher on the 32 core machine.
>
> Most of the process are running as asorcs user but some are running
as root.
So you have two users with instrumented applications.
Given the discrepancies in the information provided I'm finding it a bit
hard to understand what you're looking at.
In general, a channel's shared memory footprint can be estimated with[1]:
(nSubbuf * subbufSize) * (nCPUs + 1 iff snapshot mode is enabled) *
(nUIDs or nPIDs)
Note that the sub-buffer sizes you are using get rounded to the nearest
larger power of 2. See [2].
thanks,
kienan
[1]: https://lttng.org/docs/v2.13/#doc-channel-buffering-schemes
[2]:
https://lttng.org/man/1/lttng-enable-channel/v2.13/#doc-opt--subbuf-size
next prev parent reply other threads:[~2025-03-11 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 10:35 Gour DEV via lttng-dev
2025-03-11 13:55 ` Kienan Stewart via lttng-dev
2025-03-11 18:55 ` Kienan Stewart via lttng-dev [this message]
2025-03-12 9:19 ` Gour DEV via lttng-dev
[not found] ` <CAE9JrzhPxAzOKjk+3Z0ZEtuyYq3f_mAmPS980dNZhMe9LFPtew@mail.gmail.com>
2025-03-12 14:36 ` Kienan Stewart via lttng-dev
-- strict thread matches above, loose matches on Subject: below --
2025-03-10 14:02 Gour DEV via lttng-dev
2025-03-10 15:40 ` Kienan Stewart 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=38dab5ef-f106-4e57-9e36-b4b30015c019@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=kstewart@efficios.com \
--cc=lakshyagour10@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