by Calin Cascaval, Colin Blundell, Maged Michael, Harold W. Cain, Peng Wu, Stefanie Chiras, and Siddhartha Chatterjee for ACM Queue
TM (transactional memory) is a concurrency control paradigm that provides atomic and isolated execution for regions of code. TM is considered by many researchers to be one of the most promising solutions to address the problem of programming multicore processors. Its most appealing feature is that most programmers only need to reason locally about shared data accesses, mark the code region to be executed transactionally, and let the underlying system ensure the correct concurrent execution. This model promises to provide the scalability of fine-grain locking, while avoiding common pitfalls of lock composition such as deadlock. In this article we explore the performance of a highly optimized STM and observe that the overall performance of TM is significantly worse at low levels of parallelism, which is likely to limit the adoption of this programming paradigm.
Related Posts
Parallel Programming with Transactional Memory



2 responses so far ↓
1 Toys Toys and More Toys » Blog Archive » Software Transactional Memory: why is it only a research toy? // Dec 2, 2008 at 9:11 am
[...] Read the rest of this great post here [...]
2 Transactional memory pro and con | insideHPC // Dec 2, 2008 at 1:02 pm
[...] has a pair of pointers to ACM Queue articles pro and con transactional memory in parallel programming for multicore systems. From the (mostly) pro article [...]