Corpus ID: 245321

Snapshot Isolation Does Not Scale Either

  title={Snapshot Isolation Does Not Scale Either},
  author={V. Bushkov and Dmytro Dziuma and P. Fatourou and R. Guerraoui},
Transactional memory (TM) [11, 15] allows concurrent processes to execute operations on data items within atomic blocks of instructions, called transactions. A transaction may either commit in which case all its updates become visible to other transactions, or abort in which case all its updates are discarded. The paradigm is appealing for its simplicity but implementing it efficiently is challenging. Ideally, the TM system should not introduce any contention between transactions beyond that… Expand
4 Citations
On the use of Clocks to Enforce Consistency in the Cloud
  • 21
  • PDF
Survey on consistency conditions
  • 5
  • PDF


Inherent limitations on disjoint-access parallel implementations of transactional memory
  • 46
  • PDF
Transactional Memory: Architectural Support For Lock-free Data Structures
  • M. Herlihy, J. Moss
  • Computer Science
  • Proceedings of the 20th Annual International Symposium on Computer Architecture
  • 1993
  • 1,101
  • PDF
Software transactional memory
  • 1,062
On obstruction-free transactions
  • 65
  • PDF
Disentangling multi-object operations (extended abstract)
  • 44
  • PDF
Disjoint-access-parallel implementations of strong shared memory primitives
  • 233
The serializability of concurrent database updates
  • 976
  • PDF
Towards formally specifying and verifying transactional memory
  • 110
  • Highly Influential
Software transactional memory for dynamic-sized data structures
  • 1,083
  • Highly Influential
  • PDF
What Really Makes Transactions Faster
  • 109
  • PDF