virtual memory 4512
fOn Mon, 15 May 2006 22:38:39 +0200 in alt.folklore.computers, Terje
Pool-subpool allocation seems advantageous in situations where, as with OS control blocks, you sometimes have high rates of de--allocation and sometimes have high numbers, but only rarely in different subpools at the same time. I've used a generic subpool allocator, which doubles the total number of allocated objects each time it has to ask malloc for more memory, in such situations on projects, and as a result never had noticeable time or space problems. So I never actually had to measure the difference between that approach and regular malloc (yeah, premature optimization is the root of all evil, but I'm Scottish and cheap with other people's CPUs and bits, and dislike debugging problems when I can design to avoid them).
virtual memory 4513
science center had ported apl-360 to cms-apl. apl-360 had basicly its own subsystem monitor, terminal handler, swapper, storage manager...
And results in mbuttive working sets for fairly trivial programs in Java where garbage is rarely deallocated due to finalize rarely being called.
As with malloc and friends, there must be some bad VM implementations out there for them to build their own, unless it's a holdover from old 68K Macs without MMU.
-- Thanks. Take care, Brian Inglis Calgary, Alberta, Canada
fake address use address above to reply