ycsb-commands and parameters-related to generated payload types

Load
BIN/YCSB load mydb-p workloads/workloada-p "mydb.host=127.0.0.1"-P "mydb.port=1111"-P "recordcount=200"-P "operationc ount=10 "-P" insertorder=sorted "" Requestdistribution=zipfian "

Run
BIN/YCSB run mydb-p workloads/workloada-p "mydb.host=127.0.0.1"-P "mydb.port=1111"-P "recordcount=200"-P "Operationco unt=10 "-P" insertorder=sorted "" Requestdistribution=zipfian "

Summarize:
-P Workloads/workloada is required, but its contents can be overridden by the-p parameter.
RecordCount the entry at load. Operationcount indicates the entry at run time.
InsertOrder represents the distribution at load time. Requestdistribution represents the distribution at run time.

However, load-related parameters can affect the behavior of run.
For example, when load is used in sequential inserts, the data set is considered to be generated when run has sequential insertion of parameters.

Operationcount is not load-independent, "Requestdistribution=zipfian" is not load-independent, and load is alwaysgenerated using the form of U niform

Load, IF-P "insertorder=sorted", then the YCSB generated mode is userxxyy, where xx is the sequential value, from 1 until recordcount-1, YY is a string of numbers, This number is related to XX, all the same number of xx whose yy is the same, the final composition of the key has the same length.

This sequence of key sequences is not really orderly. Even duplicate keys are generated.

For example, key 1 and key 18 are user1863145027629296129 user63145027629296129 But obviously the result is the same key.

ycsb-commands and parameters-related to generated payload types