🚀 go-pugleaf

On Fri, 2 Apr 2004 20:28:13 +0700, Sara T. wrote:

> I am worry because my application needs to be running 24*7 and it makes
> another application on that machine cannot be run as well.

If the cause is the natural fragmentation of the heap then you need to
improve your heap usage. The likely reason for the HM doing what I
suggested is performance. By keeping the free list short the HM would have
a shorter list to sort through when a new allocation is requested.

The only solution to this is to implement your own heap management.

When we ran into this problem we were lucky. It was an isolatable
subprocess and therefore amenable to a specific solution. A simple class
was produced that effectively 'cached' allocations. This meant that when
our routine released memory it wasn't given back to the HM and could be
reused later. The class used a std::map where the key was the block size
and this proved enough for us. No attempt was made to suballocate blocks
which vastly simplified the class.

If your problem is more endemic then you may need to replace the HM
completely with one of your own. C++ is fully supportive of this but never
having done it I don't know the details. I believe that it involves
overloading the new and delete operators.

NB:My comments about the cause and internal workings of the HM are
speculation. Educated speculation perhaps but I may be completely wrong :)
-- 
Andrue Cope
[Bicester UK]