RegionTrack
Autor: | Xiupei Mei, Ernest Pobee, W. K. Chan, Hao Zhang, Shangru Wu, Bo Jiang, Xiaoxue Ma |
---|---|
Rok vydání: | 2020 |
Předmět: |
FOS: Computer and information sciences
020203 distributed computing Atomicity Correctness Linearizability Computer science Programming language Serialization media_common.quotation_subject 020207 software engineering 02 engineering and technology computer.software_genre Software Engineering (cs.SE) Computer Science - Software Engineering Debugging 0202 electrical engineering electronic engineering information engineering False positive paradox Timestamp Database transaction computer Software media_common |
Zdroj: | ACM Transactions on Software Engineering and Methodology. 30:1-49 |
ISSN: | 1557-7392 1049-331X |
DOI: | 10.1145/3412377 |
Popis: | Atomicity is a correctness criterion to reason about isolated code regions in a multithreaded program when they are executed concurrently. However, dynamic instances of these code regions, called transactions, may fail to behave atomically, resulting in transactional atomicity violations. Existing dynamic online atomicity checkers incur either false positives or false negatives in detecting transactions experiencing transactional atomicity violations. This paper proposes RegionTrack. RegionTrack tracks cross-thread dependences at the event, dynamic subregion, and transaction levels. It maintains both dynamic subregions within selected transactions and transactional happens-before relations through its novel timestamp propagation approach. We prove that RegionTrack is sound and complete in detecting both transactional atomicity violations and non-serializable traces. To the best of our knowledge, it is the first online technique that precisely captures the transitively closed set of happens-before relations over all conflicting events with respect to every running transaction for the above two kinds of issues. We have evaluated RegionTrack on 19 subjects of the DaCapo and the Java Grande Forum benchmarks. The empirical results confirm that RegionTrack precisely detected all those transactions which experienced transactional atomicity violations and identified all non-serializable traces. The overall results also show that RegionTrack incurred 1.10x and 1.08x lower memory and runtime overheads than Velodrome and 2.10x and 1.21x lower than Aerodrome, respectively. Moreover, it incurred 2.89x lower memory overhead than DoubleChecker. On average, Velodrome detected about 55% fewer violations than RegionTrack, which in turn reported about 3%-70% fewer violations than DoubleChecker. 48 pages |
Databáze: | OpenAIRE |
Externí odkaz: |