Re: [boost] Re: Challenge: pool allocator

From: Greg Colvin (greg_at_[hidden])
Date: 2000-07-06 03:08:02

From: <mtsirkin_at_[hidden]>
>
> Another issue worth considering IMHO is the locality principle:
> when you have a container (e.g. vector) and inside it
> a pointer to allocated memory, you might want to try to
> put the allocated chunk as close as possible to the original 
> object itself, to reduce the amount of memory pages used.
> 
> We use a commercial memory management library that provides such 
> allocator, but I know of no public domain implemntation that can do 
> this.
> Or testing shows that when memory usage is high, results can be 
> imressive, performance-wise.

What is the interface to this allocator?  That is, how do you
tell it that you want two objects to be on the same memory
page?  Or does it figure this out for itself?