{antidote_pb_ips, ['127.0.0.1']}
. {antidote_pb_port, [8087]}
.{driver, basho_bench_driver_antidote_pb}
.{operations, [{op1, 4}, {op2, 1}]}.
op1
and op2
, where out of 5 operations op1
will be executed 4 times, while op2
will be executed 1 time. The possible operations are defined in the driver.txn
, update_only_txn
, read_only_txn
, append
, read
.read
or append
, e.g.:{num_reads, 10}.
The number of reads done for each transaction, that do reads.{num_updates, 10}.
The number of updates done for each transaction, that do updates.{sequential_reads, false}.
If set to true
, the client will send each read (of a total {num_reads, X}
) in a different antidote:read_objects call. When set to false
, all ({num_reads, X}
) reads will be sent in a single read_objects call, which is faster, as Antidote will process them in parallel.{sequential_writes, false}.
The same as {sequential_reads, Boolean}.
but with updates.txn
{num_reads, X}
parameter. Then it updates {num_updates, X}
.update_only_txn
{num_updates, X}
parameter in the config file.read_only_txn
{num_reads, X}
parameter in the config file.append
read
driver:run/4
may be:{ok, NewState}
— operation completed successfully{error, Reason, NewState}
— operation failed but the driver can continue processing (i.e. recoverable error){stop, Reason}
— operation failed; driver can’t/won’t continue processing{'EXIT', Reason}
— operation failed; driver crashed