Memory Pool performance

[itix]

Well...

Allocating new puddles can be time consuming. Thus if you are doing lot of allocations try minimize need of new puddles.

And for puddle sizes... I think it is better choose something like 4000 than 4200. Puddle sizes are always rounded up (if at all, on OS3 they arent).

[itix]

In general AllocPooled() is not probably any slower than AllocMem(). But of course if Exec finds out that all puddles are full then Exec must call AllocMem() as well. Thus it is always better oversize puddles bit rather than undersize.

Another thing is FreePooled(). FreeMem() is very simple call but FreePooled() must go through all puddles. In the worst case scenario calling FreePooled() can be very demanding. Piru investigated this issue.. Must ask him :-D

My understanding of the system is that it just allocates memory rounded to the puddlesize and allows sub allocations for several small objects within a single puddle..

Correct. If memory allocation is larger than treshold value then new puddle is allocated.