DSpace Repository

Garbage Collection is Fast, But a Stack is Faster

Show simple item record

dc.creator Miller, James S.
dc.creator Rozas, Guillermo J.
dc.date 2004-10-08T20:34:37Z
dc.date 2004-10-08T20:34:37Z
dc.date 1994-03-01
dc.date.accessioned 2013-10-09T02:46:10Z
dc.date.available 2013-10-09T02:46:10Z
dc.date.issued 2013-10-09
dc.identifier AIM-1462
dc.identifier http://hdl.handle.net/1721.1/6622
dc.identifier.uri http://koha.mediu.edu.my:8181/xmlui/handle/1721
dc.description Prompted by claims that garbage collection can outperform stack allocation when sufficient physical memory is available, we present a careful analysis and set of cross-architecture measurements comparing these two approaches for the implementation of continuation (procedure call) frames. When the frames are allocated on a heap they require additional space, increase the amount of data transferred between memory and registers, and, on current architectures, require more instructions. We find that stack allocation of continuation frames outperforms heap allocation in some cases by almost a factor of three. Thus, stacks remain an important implementation technique for procedure calls, even in the presence of an efficient, compacting garbage collector and large amounts of memory.
dc.format 94049 bytes
dc.format 389294 bytes
dc.format application/octet-stream
dc.format application/pdf
dc.language en_US
dc.relation AIM-1462
dc.title Garbage Collection is Fast, But a Stack is Faster


Files in this item

Files Size Format View

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record

Search DSpace


Advanced Search

Browse

My Account