[pulseaudio-discuss] PulseAudio does eat RAM with "lock-memory"

[Arun Raghavan]

On Thu, 2012-01-05 at 02:41 +0200, Roman Beslik wrote:
> Hello.
> 
> The wiki page
> http://pulseaudio.org/wiki/MemoryConsumption
> reassures us that PulseAudio will not eat our RAM: PulseAudio allocates 
> 64 MiB of address space, but the big part of that address space is not 
> assigned to RAM, therefore all is o'kay. However, if "lock-memory = yes" 
> in "/etc/pulse/daemon.conf", than PulseAudio does eat RAM. Because no 
> real-time process may have its address space unassigned (or assigned to 
> a swap, BTW). If you agree, I will add real-time considerations to the 
> wiki page.

Please do. Perhaps it also makes sense to tune down the SHM pool size
for those cases.

-- Arun