Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data.

Tamar Domani

dblp:08/2853 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 2000
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2 · 2 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Runtime systems and virtual machines · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Parallel and multicore computing · 100%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Runtime systems and virtual machines
garbage collection
0.012000
A generational on-the-fly garbage collector for Java · PLDI 2000
Runtime systems and virtual machines › garbage collection
generational garbage collection
0.012000
A generational on-the-fly garbage collector for Java · PLDI 2000
Runtime systems and virtual machines › garbage collection
on-the-fly garbage collection
0.012000
A generational on-the-fly garbage collector for Java · PLDI 2000
Parallel and multicore computing › multiprocessor system
multiprocessor server
0.012000
A generational on-the-fly garbage collector for Java · PLDI 2000
Parallel and multicore computing › thread-level parallelism
multithreaded applications
0.012000
A generational on-the-fly garbage collector for Java · PLDI 2000

Methods — techniques the papers use, named apart from their topics

concurrent collection · 0.1
YearPublicationVenuePosition
2000 Implementing an On-the-Fly Garbage Collector for Java
abstract
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 th...
Tamar Domani, Elliot K. Kolodner, Ethan Lewis, Eliot E. Salant, Katherine Barabash, Itai Lahan, Yossi Levanoni, Erez Petrank, Igor Yanover
ISMM1
2000 A generational on-the-fly garbage collector for Java
abstract
An on-the-fly garbage collector does not stop the program threads to perform the collection. Instead, the collector executes in a separate thread (or process) in parallel to the program. On-the-fly collectors are useful for multi-threaded applications running on multiprocessor servers, where it is important to fully utilize all processors and provide even response time, especially for systems for which stopping the threads is a costly operation.
Tamar Domani, Elliot K. Kolodner, Erez Petrank
PLDI1