Matches in DBpedia 2016-04 for { <http://citation.dbpedia.org/hash/a00c9e03b161e5fa6a6342ba36cb562ad9ef02e5b6850bfdec9a1e80a398f3a9> ?p ?o }
Showing triples 1 to 7 of
7
with 100 triples per page.
- a00c9e03b161e5fa6a6342ba36cb562ad9ef02e5b6850bfdec9a1e80a398f3a9 date "1993-01-22".
- a00c9e03b161e5fa6a6342ba36cb562ad9ef02e5b6850bfdec9a1e80a398f3a9 first "Benjamin".
- a00c9e03b161e5fa6a6342ba36cb562ad9ef02e5b6850bfdec9a1e80a398f3a9 isCitedBy Garbage_collection_(computer_science).
- a00c9e03b161e5fa6a6342ba36cb562ad9ef02e5b6850bfdec9a1e80a398f3a9 last "Zorn".
- a00c9e03b161e5fa6a6342ba36cb562ad9ef02e5b6850bfdec9a1e80a398f3a9 publisher "Department of Computer Science, University of Colorado Boulder".
- a00c9e03b161e5fa6a6342ba36cb562ad9ef02e5b6850bfdec9a1e80a398f3a9 quote "Conservative garbage collection does not come without a cost. In the programs measured, the garbage collection algorithm used 30–150 per cent more address space than the most space efficient explicit management algorithm. In addition, the conservative garbage collection algorithm significantly reduced the reference locality of the programs, greatly increasing the page fault rate and cache miss rate of the applications for a large range of cache and memory sizes. This result suggests that not only does the conservative garbage collection algorithm increase the size of the address space, but also frequently references the entire space it requires.".
- a00c9e03b161e5fa6a6342ba36cb562ad9ef02e5b6850bfdec9a1e80a398f3a9 title "The Measured Cost of Conservative Garbage Collection".