[gclist] Allocation sizes under conservative collection.
Charles Fiterman
cef@geodesic.com
Mon, 17 Nov 1997 08:22:54 -0600
I'm coming to the conclusion that allocation
sizes under a page on a conservative collector
should be only powers of two. The user should
have an escape such as the ability to create
memory pools of special sized objects.
For most applications the waste seems to be
negative. That is you use more objects on
a page and that overcomes having waste inside
of objects.
Things like mark and gcBase run much faster
using a shift rather than a divide or a
lookup.
-
Charles Fiterman Geodesic Systems
414 North Orleans Suite 410 Phone 312 832 1221 x223
Chicago IL 60610-4418 FAX 312 832 1230
http://www.geodesic.com
A young man saw a product advertised in a magazine that said
"Guaranteed 100% effective against bugs when properly used."
He sent away and got two blocks of wood with the instructions
"Place bug on block A, strike sharply with block B." Debuggers
are like that, and you can get stung while using them. Great
Circle tries to be something better than that.