[pulseaudio-discuss] Hard-coded allocation of 64 MB of memory upfront too big in some scenarios

CJ van den Berg cj at vdbonline.com
Tue Aug 26 06:26:46 PDT 2008

On Tue, Aug 26, 2008 at 01:10:13PM +0000, rdiezmail-pulseaudio at yahoo.de wrote:
> I'm compiling the client library for an embedded PowerPC target
> without shared memory or the like. In fact, the device has much less
> memory than a standard PC.
> In this scenario, PA_MEMPOOL_SLOT_SIZE is set to a rather big value in pulsecore/memblock.c :
> #define PA_MEMPOOL_SLOT_SIZE (64*1024)
> That causes allocation of 64 MB at once later on, before establishing
> any audio connections to the server. If you're using the client
> library's asynchronous interface to play a simple sound say from a
> file, you don't need that much memory, do you? How much should I go
> for?

The memory is *not* allocated, it is only mapped. No actual memory will
be used until a client connects (via shared memory), and even then, it's
only 64K per client.

CJ van den Berg

mailto:cj at vdbonline.com
  xmpp:cj at vdbonline.com

More information about the pulseaudio-discuss mailing list