2 ms·
there is no a prior reason to not assume that a freshly allocated tree occupies a contiguous region of memory But I'm sure you'll also agree that a freshly all
by bunderbunder 15y ago
there is no a prior reason to not assume that a freshly allocated tree occupies a contiguous region of memory
But I'm sure you'll also agree that a freshly allocated tree probably hasn't been alive for long and hasn't seen much activity. :)
- carterschonwald 15y agoVery true! Hence the part where I'm thinking out loud regarding how the gc ordering of data after a copy/compact (in the one generation gc) impacts locality. And I suppose this also applies to more modern gc setups like multiple generations or parallel collection. Is there some notion of data locality that we can formalize and analyze for at least simplified versions of modern memory hierarchy? How well do standard gc algorithms perform when analyzed thusly? How efficient can each style of gc algorithm be if it's designed to optimize locality? It clearly has some relation to optimal caching optimization problems, but with more explicit interdependencies. It's also seemingly both an online and offline problem in terms of how to analyze it, but I need to think on it more