[gclist] Program behaviour models.
Wed, 15 Jan 1997 08:54:37 -0600
Instead of having a one size fits all model for
program behavior perhaps programs could inform
collectors about which model is most valuable.
0. Program dominated by execution time.
1. Program dominated by page swap time.
0. Program expands to a size and keeps it.
2. Program expands at peak period then contracts.
It seems these flags apply to whole programs, classes
and functions. Telling the collector this collection
class will expand to a peak and live on might give
different behavior for its allocated objects.
Users would have these flags for tuning and not worry
about them unless it became important to do so.
Charles Fiterman Geodesic Systems
414 North Orleans Suite 410 Phone 312 832 1221 x223
Chicago IL 60610-4418 FAX 312 832 1230
A computer language without garbage collection
is like a city without garbage collection.