Re: [squid-users] Memory pools: why use them?

> On Tue, 2004-08-31 at 10:42 +0200, Matus UHLAR - fantomas wrote:
> > IIUC, they are blocks of reserved/unused memory, which squid maintains
> > itself instead of running malloc/free on the memory (and letting the
> > malloc library to maintain the memory)

On 31.08 19:23, Robert Collins wrote:
> A Memory pool is indeed that. The exact nature depends on the mempool
> implementation in question (which has changed over time), and in 3.0
> will be somewhat dynamic, allowing for both slab allocators and simple
> os caching pools.
>
> However, we do get folk asking this fairly often, and I'm seriously
> considering removing the configure option completely.

in what way? to have that behavior permanent, or to keep things at library
malloc? Does squid handle its memory in such efficient way that using
malloc/free would have strong performance impact?

-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Micro$oft random number generator: 0, 0, 0, 4.33e+67, 0, 0, 0...