ACM Home Page
Please provide us with feedback. Feedback
Design tradeoffs in modern software transactional memory systems
Full text PdfPdf (159 KB)
Source ACM International Conference Proceeding Series; Vol. 81 archive
Proceedings of the 7th workshop on Workshop on languages, compilers, and run-time support for scalable systems table of contents
Houston, Texas
Pages: 1 - 7  
Year of Publication: 2004
Authors
Virendra J. Marathe  University of Rochester, Rochester, NY
William N. Scherer  University of Rochester, Rochester, NY
Michael L. Scott  University of Rochester, Rochester, NY
Sponsors
: University of Houston
: The Texas Learning & Computation Center
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 8,   Downloads (12 Months): 46,   Citation Count: 19
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1066650.1066660
What is a DOI?

ABSTRACT

Software Transactional Memory (STM) is a generic non-blocking synchronization construct that enables automatic conversion of correct sequential objects into correct concurrent objects. Because it is nonblocking, STM avoids traditional performance and correctness problems due to thread failure, preemption, page faults, and priority inversion.In this paper we compare and analyze two recent object-based STM systems, the DSTM of Herlihy et al. and the FSTM of Fraser, both of which support dynamic transactions, in which the set of objects to be modified is not known in advance. We highlight aspects of these systems that lead to performance tradeoffs for various concurrent data structures. More specifically, we consider object ownership acquisition semantics, concurrent object referencing style, the overhead of ordering and bookkeeping, contention management versus helping semantics, and transaction validation. We demonstrate for each system simple benchmarks on which it outperforms the other by a significant margin. This in turn provides us with a preliminary characterization of the applications for which each system is best suited.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
2
3
 
4
C. Cole and M. P. Herlihy. Snapshots and Software Transactional Memory. In Proceedings of Workshop on Concurrency and Synchronization in Java Programs, 2004.
 
5
K. Fraser. Practical Lock-Freedom. Technical Report UCAM-CL-TR-579, Cambridge University Computer Laboratory, February 2004.
 
6
K. Fraser and T. Harris. Concurrent Programming without Locks. Submitted for publication.
7
 
8
9
10
11
12
 
13
D. Lea. Concurrency JSR-166 Interest Site. http://gee.cs.oswego.edu/dl/concurrency-interest/.
 
14
V. J. Marathe and M. L. Scott. A Qualitative Survey of Modern Software Transactional Memory Systems. Technical Report TR 839, Department of Computer Science, University of Rochester, June 2004.
 
15
W. N. Scherer III and M. L. Scott. Contention Management in Dynamic Software Transactional Memory. In Proceedings of Workshop on Concurrency and Synchronization in Java Programs, pages 70--79, 2004.
16
 
17
18

CITED BY  19
Collaborative Colleagues:
Virendra J. Marathe: colleagues
William N. Scherer: colleagues
Michael L. Scott: colleagues