This repository has been archived by the owner on Sep 27, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 623
Epoch Based Transaction Management
Yingjun Wu edited this page Mar 22, 2017
·
1 revision
Peloton can support highly scalable transaction processing on modern multi-core architectures. It implements an epoch-based transaction management scheme for avoiding redundant centralized contention points, where a DBMS thread has to race for shared resources with other threads. A DBMS can confront (at least) three contention points during transaction processing:
-
timestamp acquisition, where each worker thread acquires a timestamp for its corresponding transaction;
-
garbage collection, where each GC thread checks the progress of each worker thread for detecting expired versions;
-
logging, where each logger thread persists logs into secondary storage.