Re: When does manually allocated memory get released?

Well there definitely seems to be some differing schools of thought on
this one. I'm thinking that a hybrid approach. Maybe not specifcally
doing a %dealloc but registering the CEETREC to do an end actgrp since it
will be named. That way the activation group always gets destroyed and
the dealloc is always handled by the system. One qustion though.... why
would the %dealloc be more overhead than the system doing the same thing
on its own?


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



"Mark S. Waterbury" <mark.s.waterbury@xxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
10/08/2010 09:38 AM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: When does manually allocated memory get released?






Unless you are talking about a very long-running server program, like
a service that listens on a socket or a data queue, and is essentially a
"never ending" job, there is really no point to ever doing a DEALLOC.
This just adds unnecessary overhead. The ILE heaps perform much faster
if all you ever do is ALLOC, because internally it just advances the
pointer into the free space, and does not have to worry about "holes".

So, for most jobs, it is far more efficient to just wait until
end-of-job and let the system take care of "throwing away" the entire
heap, rather than incurring all of the overhead to issue DEALLOCate each
chunk of storage you ALLOCated.