Re: lttng-dev Digest, Vol 203, Issue 7

Hi, Kienan Sorry for the late reply. Looks like in buster the memory is allocated by lttng-consumerd reserved I buster, the rss is less than the VIRT root@localhost:~# COLUMNS=500 top -b -n 1 | grep lttng PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 4095 root

Re: lttng-dev Digest, Vol 203, Issue 7

Thanks Kienan for digging this and explaining the behaviour, Looks like this option is not present in the version I am using v2.13.5 and the MAP_POPULATE is enabled by default there /* memory_map: mmap */ memory_map = mmap(NULL, memory_map_size, PROT_READ | PROT_WRITE, MAP_SHARED | LTTNG_MAP_POPU

Memory Consumption High After Upgrading to 2.13 from 2.10

Hello, I have recently upgraded from lttng 2.10 to 2.13 as part of servers migration from buster to bookworm. lttng 2.10.6 - KeKriek to lttng 2.13.9 - Nordicité I see an increase in memory consumption upto 11Gig after my recent upgrade. In buster root@localhost:~# top -b -n 1 | grep lttng PID

Re: Memory Consumption High After Upgrading to 2.13 from 2.10

Hi, Kienan I am attaching an screen recording of the behaviour I am seeing in this mail. The behaviour is same irrespective of the device i use, sorry for miscommunication in the npocs output (I assumed it was 32), but other than that all outputs are same (except the hostname as there are multiple

Memory Consumption High After Upgrading to 2.13 from 2.10

Hello, I have recently upgraded from lttng 2.10 to 2.13 as part of servers migration from buster to bookworm. lttng 2.10.6 - KeKriek to lttng 2.13.9 - Nordicité I see an increase in memory consumption upto 11Gig after my recent upgrade. In buster root@localhost:~# top -b -n 1 | grep lttng PID