Adding transactional_splinterdb into YCSB #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Each operation takes `Transaction`. - `DoTransaction(Transaction *)` runs the given number of operations. And the number of operations is set by the property, `opspertransaction`.
- Each operation takes `Transaction` - `DoTransaction(Transction *)` runs the given number of operations. - The number of operations is set by `opspertransaction` property.
* Adding RocksDB's (Pessimistic)TransactionDB * Adding RocksDB's OptimisticTransactionDB
|
This PR was supposed to be used for only transactional_splinterdb, but it has RocksDB's TransactionDBs(pessimistic/optimistic) as well as transactional_splinterdb. |
The problem was that an aborted transaction gets new keys from a generator. It should do with keys that it originally tried. Each transaction stores operations and replays until it commits.
* Fixed the number of operations for each thread * Added a sample workload spec for transactional databases * Implemented more strict isolation for RocksDB Transaction Based on the examples from the official RocksDB repo, this code implements `Read committed with multiple snapshot`, which is stronger than snapshot isolation/read committed without snapshot. * Minor code updates to handle transaction conflict * Added abort_cnt
* Fixed an error when non-transactional databases * Minor fixes for RocksDB to get snapshots
* Implemented various isolation levels This commit makes transactional splinterdb and rocksdb support various isolation levels. The scripts, `run_rocksdb.sh` and `run_splinterdb.sh`, will run ycsb benchs with varying parameters. * fixed a bug when running without ops_per_transaction
This commit makes transactional splinterdb and rocksdb support various isolation levels. The scripts, `run_rocksdb.sh` and `run_splinterdb.sh`, will run ycsb benchs with varying parameters.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to add a new transactional_splinterdb into this benchmark.
Transaction.DoTransaction()runs the given number of operations.opspertransactionproperty.