Record and re-use allocation patterns to speed startup, reduce fragmentation #7
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Long ago I remember a malloc-variant which recorded the sequence and size of allocations (and deallocations) from program startup until some point later in time. The goal was to record into a file that allocation pattern so that it could be included with the program in its final form. The result was that applications could startup faster and with much less memory fragmentation because the allocator knew what was going to happen and it pre-allocated and laid out space to match that pattern.
That would be interesting in and of itself. Taken a bit further one could keep track of allocation patterns and predict to some extent groups of future allocations based on current patterns. (maybe)