Very concurrent mark-&amp;-sweep garbage collection without fine-grain synchronization

Huelsbergen, Lorenz; Winterbottom, Phil

doi:10.1145/286860.286878

Cited by 29 publications

(26 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Blazes recognizes that the composition of a confluent replicated graph store and a confluent deadlock detector yields a confluent composite dataflow, and allows the system to execute without synchronization. The garbage collection component would be annotated as non-confluent but-as is common practice [41]-partitioned into generations or "epochs." If the dataflow is enhanced to produce sealing punctuations that indicate when individual allocators will produce no more edges within a given epoch, Blazes can synthesize a simple, barrier-based coordination strategy that prevents the garbage collector from executing until the graph partition is sealed-that is, the mark phase has ended for a given epoch.…”

Section: Flow-level Consistencymentioning

confidence: 99%

Consistency without borders

Alvaro

Bailis

Conway

et al. 2013

Proceedings of the 4th Annual Symposium on Cloud Computing

View full text Add to dashboard Cite

Distributed consistency is a perennial research topic; in recent years it has become an urgent practical matter as well. The research literature has focused on enforcing various flavors of consistency at the I/O layer, such as linearizability of read/write registers. For practitioners, strong I/O consistency is often impractical at scale, while looser forms of I/O consistency are difficult to map to application-level concerns. Instead, it is common for developers to take matters of distributed consistency into their own hands, leading to application-specific solutions that are tricky to write, test and maintain.In this paper, we agitate for the technical community to shift its attention to approaches that lie between the extremes of I/O-level and application-level consistency. We ground our discussion in early work in the area, including our own experiences building programmer tools and languages that help developers guarantee distributed consistency at the application level. Much remains to be done, and we highlight some of the challenges that we feel deserve more attention.

show abstract

Section: Flow-level Consistencymentioning

confidence: 99%

Consistency without borders

Alvaro

Bailis

Conway

et al. 2013

Proceedings of the 4th Annual Symposium on Cloud Computing

View full text Add to dashboard Cite

show abstract

“…Instead of changing all header block's colour entries and all colour flags of inner blocks during the sweep phase, the colour is at first left unchanged during the sweep phase. Only at the end of the sweep phase, a f lip occurs in which the meaning of black and white is swapped as originally proposed by Lamport [13] and used by many implementations [10,3,6,11]. This poses a small additional overhead on the shading code, since now the values for white and white f lags are variables and not constants.…”

Section: Sweep Phasementioning

confidence: 99%

Realtime garbage collection in the JamaicaVM 3.0

Siebert

2007

Proceedings of the 5th International Workshop on Java Technologies for Real-Time and Embedded Systems - JTRES '07

View full text Add to dashboard Cite

This paper provides an overview of the realtime garbage collector used by the RTSJ Java Virtual Machine JamaicaVM. A particular emphasis will be made on the improvements made in with release 3.0 JamaicaVM.The JamaicaVM garbage collector is incremental to an extreme extent: single incremental steps of the garbage collector correspond to scanning only 32 bytes of memory and have a worst-case execution time in the order of one µsec. The JamaicaVM garbage collector uses automatic pacing, making the system easier to configure than a garbage collector using explicit pacing that requires information on the application's allocation rate.The recent improvements of the garbage collector that will be present in this paper include support for automatic heap expansion; reduction of the memory overhead for garbage collector internal structures; and significant performance optimisation such as a faster write-barrier and a sweep phase that does not need to touch the objects and therefore reduces the number of cache misses caused during sweep.

show abstract

“…We introduce a color toggle similar to previous work [24,20,8,4,21]. Instead of changing the color for each black object, the color toggle simply changes the interpretation of the colors.…”

Section: Color Togglementioning

confidence: 99%

Implementing an on-the-fly garbage collector for Java

et al. 2000

View full text Add to dashboard Cite

Java uses garbage collection (GC) for the automatic reclamation of computer memory no longer required by a running application. GC implementations for Java Virtual Machines (JVM) are typically designed for single processor machines, and do not necessarily perform well for a server program with many threads running on a multiprocessor. We designed and implemented an on-the-fly GC, based on the algorithm of Doligez, Leroy and Gonthier [13,12] (DLG), for Java in this environment. An on-the-fly collector, a collector that does not stop the program threads, allows all processors to be utilized during collection and provides uniform response times. We extended and adapted DLG for Java (e.g., adding support for weak references) and for modern multiprocessors without sequential consistency, and added performance improvements (e.g., to keep track of the objects remaining to be traced). We compared the performance of our implementation with stop-the-world mark-sweep GC. Our measurements show that the performance advantage for our collector increases as the number of threads increase and that it provides uniformly low response times.

show abstract

Very concurrent mark-&-sweep garbage collection without fine-grain synchronization

Cited by 29 publications

References 17 publications

Consistency without borders

Consistency without borders

Realtime garbage collection in the JamaicaVM 3.0

Implementing an on-the-fly garbage collector for Java

Contact Info

Product

Resources

About