Re: [Boost-users] [Pool] Why is pool allocator slower than ordinaryallocator?

Subject: Re: [Boost-users] [Pool] Why is pool allocator slower than ordinaryallocator?
From: Mr.C64 (c64gio_at_[hidden])
Date: 2012-05-05 10:36:41

On Sat, May 5, 2012 at 1:26 PM, John Maddock <boost.regex_at_[hidden]> wrote:

"FYI Boost.Pool isn't designed for or optimised for that usage - it's
> designed for lots of fixed-sized blocks, as happens in a list (or even a
> map or a set), it's not really designed for fast performance with variable
> sized blocks as happens in a string or a vector."
>
>
Do you know of any open-source allocator (available in Boost or elsewhere),
that can be used to *quickly* allocate instances of std::wstring, using an
allocation pattern like the one showed in the following blog post?

 http://tinyurl.com/cu3lzwz

Thanks,
Mr.C64