This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Less good ;-) results from Rittle's string allocator
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: libstdc++ at gcc dot gnu dot org
- Cc: pedwards at disaster dot jaj dot com
- Date: Wed, 28 Nov 2001 02:55:04 -0600 (CST)
- Subject: Re: Less good ;-) results from Rittle's string allocator
- Organization: Networks and Infrastructure Lab (IL02/2240), Motorola Labs
- References: <3C03962D.A893E65D@unitus.it>
> More specifically, how often will memory clients /other than basic_string/
> be requesting chunks of a half-K at a time?
[...]
> Let me throw out an idea I had while typing the last paragraph: we could
> make the _MAX_BYTES a template parameter of the allocator:
> old: __default_alloc_template<true,0>
> new: __default_alloc_template<true,0, _MAX_BYTES=256>
> or something similar. Then basic_string can have its own memory pool.
Yuck was the first thing to come to my mind. BTW, did you see the
comment that, under the current implementation, you can't just change
_MAX_BYTES?