Skip to content

updated description for mutli-exec - for issue 212 #219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 26, 2023
Merged

updated description for mutli-exec - for issue 212 #219

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...ication/test-suites/memtier_benchmark-1Mkeys-hash-transactions-multi-exec-pipeline-20.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
version: 0.4
name: memtier_benchmark-1Mkeys-hash-transactions-multi-exec-pipeline-20
description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data size of 100 Bytes for each key, focusing on the MULTI EXEC scenario. TODO - this descriotion needs fixing. We either need a preload command to populate 1M keys, or we need to modify this description.
description: Runs memtier_benchmark for MULTI EXEC scenario - executing commands as a transaction. The transaction sets fields in a hash, checks if they exist, retrieves them and finally deletes them. At the end of execution there are no keys in the database.
tested-groups:
- transactions
- hash
Expand Down