stephentu / silo Goto Github PK

In order to capture anti-dependencies, it is necessary for commit TID generation to use the current global epoch, not the worker's local epoch. Here is an example why (thanks to eddie for the counter-example):

(1) t1 begins in epoch 0
(2) t1 writes x => version 1 (in write set only)
(3) epoch changes to 1
(4) t2 reads x @ version 0
(5) t2 writes y
(6) t2 commits in epoch 1
(7) t1 commits in epoch 0.

The fix is easy, but I will not apply it until after the camera ready is submitted.

There are serveral question's about silo's OCC writeset lock during commit time.
1, Is the lock always set to true when the tuple is a inserted one?
2, If tuples are modified ones, are there any locks during commit time? Does Silo create a new version in thread-or-numanode local memory and update the index?

Hi,
I followed the readme file and I keep getting this message while trying to compile the benchmark.

btree_impl.h:213:7: error: ‘struct btree<testing_concurrent_btree_traits>::leaf_node’ has no member named ‘is_layer’

Any ideas ?