STM with Transparent API Considered Harmful

Carvalho, Fernando Miguel; Cachopo, João

doi:10.1007/978-3-642-24650-0_28

Cited by 3 publications

(1 citation statement)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Transactional memory [26] aims to simplify concurrent programming. Though the performance of transactional memory systems has been extensively optimized [22], overheads due to bookkeeping and false conflicts can lead to unsatisfactory performance [6,7], even in high-performance TMs like TL2 [12] and LarkTM [52].…”

Section: Related Workmentioning

confidence: 99%

Type-aware transactions for faster concurrent code

Herman

Inala

Huang

et al. 2016

Proceedings of the Eleventh European Conference on Computer Systems

View full text Add to dashboard Cite

It is often possible to improve a concurrent system's performance by leveraging the semantics of its datatypes. We build a new software transactional memory (STM) around this observation. A conventional STM tracks read-and writesets of memory words; even simple operations can generate large sets. Our STM, which we call STO, tracks abstract operations on transactional datatypes instead. Parts of the transactional commit protocol are delegated to these datatypes' implementations, which can use datatype semantics, and new commit protocol features, to reduce bookkeeping, limit false conflicts, and implement efficient concurrency control. We test these ideas on the STAMP benchmark suite for STM applications and on our own prior work, the Silo high-performance in-memory database, observing large performance improvements in both systems.

show abstract