Snapshot Isolation Anomalies Detection in Software Transactional Memory

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Some performance issues of transactional memory are caused by unnecessary abort situations where non serializable and yet non conflicting transactions are scheduled to execute concurrently. Smartly relaxing the isolation properties of transactions may overcome these issues and attain considerable performance improvements. However, it is known that relaxing isolation restrictions may lead to runtime anomalies. In some situations, like database management systems, developers may choose that compromise, hence avoiding anomalies explicitly. Memory transactions protect the state of the program, therefore execution anomalies may have more severe consequences in the semantics of programs. So, the compromise between a relaxed isolation strategy and enforcing the necessary program correctness is harder to setup. The solution we devise is to statically analyse programs to detect the kind of anomalies that emerge under snapshot isolation. Our approach allows a compiler to either warn the developer about the possible snapshot isolation anomalies in a given program, or possibly inform automatic correctness strategies to ensure Serializability.
Original languageUnknown
Title of host publicationINForum
PublisherUniversidade do Minho
Pages31-42
Publication statusPublished - 1 Jan 2010
EventInForum -
Duration: 1 Jan 2010 → …

Conference

ConferenceInForum
Period1/01/10 → …

Cite this