Skip to content
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.

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

[core] limit number of client threads based on op count. #1323

Merged
merged 7 commits into from
Sep 7, 2019
Merged
Changes from 1 commit
Commits
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
Next Next commit
Update README.md
#1212

The YCSB readme is as the following, which is a little misleading.Because we can't use '-p durability=false' to disable durability. Instead it worked when I used '-p durability=SKIP_WAL'. The readme should be written more clearly.

durability: Whether or not writes should be appended to the WAL. Bypassing the WAL can improve throughput but data cannot be recovered in the event of a crash. The default is true.
  • Loading branch information
adally authored Nov 16, 2018
commit ea0af299a36d4978403cfd0baca6310bb8034e93
2 changes: 1 addition & 1 deletion hbase12/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,5 +23,5 @@ See `hbase098/README.md` for a quickstart to setup HBase for load testing and co
## Configuration Options
In addition to those options available for the `hbase098` binding, the following options are available for the `hbase12` binding:

* `durability`: Whether or not writes should be appended to the WAL. Bypassing the WAL can improve throughput but data cannot be recovered in the event of a crash. The default is true.
* `durability`: Whether or not writes should be appended to the WAL. Bypassing the WAL can improve throughput but data cannot be recovered in the event of a crash. The default is true. We can set it to flase by option '-p durability=SKIP_WAL'.