Quote Originally Posted by John E View Post
performance-wise, boost::fast_pool_allocator isn't particularly fast
the boost pool allocators are designed to be used when frequent uniform de/allocations of fixed size types are needed ( plus non-contiguous if fast_pool_allocator is used ). A different de/allocattion pattern will have a time and space penalty with respect to the usual heap allocators, so you should not use them interchangeably ( so, I don't think that the default allocator employs any free-list based pool mechanism for general de/allocations ).