On Tue, 31 Aug 2004, Matus UHLAR - fantomas wrote:
> 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?
Just to take away the "memory_pools on/off" configuration directive as it
does not make much sense to have this direcive. The configure
--disable-mempools directive is sufficient and serves a real purpose.
The main reason why the configuration directive exists is to initially
make it easier to proof that the use of memory pools do make a benefit.
This is already well proven. In fact the configuration directive probably
should had gone away even before the first STABLE release with memory
pools support, remaining only as a configure --disable-mempools directive.
The --disable-mempools configure directive is still needed, but for other
reasons (debugging).
Regards
Henrik
Received on Tue Aug 31 2004 - 09:13:50 MDT
This archive was generated by hypermail pre-2.1.9 : Wed Sep 01 2004 - 12:00:03 MDT