{ Please note that top-posting is discouraged in this group. -mod }

These days I spent a lot of time researching Boehm GC, Hoard/
HeapLayers/reaps, streamflow, dlmalloc, etc.

Yes, "GC Allocator" is a region allocator. It's no innovation. But:

This (ScopeAlloc) is not a normal region allocator. All ScopeAlloc
instances in the same thread share their freelist. This makes you can
define a lot of ScopeAlloc instances (depends your needs). You even
can define a ScopeAlloc instance for each allocation.

Most allocators optimize allocating a lot of objects. If ONE allocator
instance only allocates ONE object instance, they become slower than a
normal new/delete allocation.

Since you can define a lot of ScopeAlloc instances as you need, So It
doesn't waste too much memory as normal region allocators.

ScopeAlloc is useful. For example:

* When you are writing an io component (eg. a word file writer:
http://xushiwei.com/the-fastest-word-file-writer).
* When you are writing a search engine.
* When you are writing a layout render engine.
* When you are responding a http request.

And I don't think it is all of C++ memory management. if you implement
algorithms that are related to t (that is, how many time of the
algorithm spent is unsure.), ScopeAlloc doesn't fit you directly.

Last, I think that we need a standard region allocator. Yes, maybe it
is have limits. But just like unique_ptr (auto_ptr), scoped_ptr, they
are useful but not a general solution.

On 4月29日, 上午5时58分, Yongwei Wu gmail.com> wrote: