|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
public static interface ThroughputMaster.ConfigurationOptions
Configuration options for the ThroughputMaster.
| Field Summary | |
|---|---|
static String |
ASYNCHRONOUS
When true the client writes will use the asynchronous
API. |
static String |
INC_RANGE
The keys for insert operations are selected by choosing a random key from the legal key range as a starting key and then advancing by a random number selected from [1:incRange]. |
static String |
MAX_KEYS_PER_OP
The maximum #of keys to be used in each operation submitted by a client. |
static String |
NAMESPACE
The namespace for the indices registered by this job. |
static String |
NPARTITIONS
The #of index partitions (pre-splits the index). |
static String |
OPERATION_COUNT
The #of index operations to execute per client. |
static String |
SEED
The seed used for random data generation (default is 0, which uses a different seed for each run). |
static String |
START_KEY_PARTITIONS
Boolean option specifies whether the key ranges for client operations are disjoint or shared. |
static String |
ZOOKEEPER_UPDATE_INTERVAL
After every N operations, where N is specified by this property, the state of the client will be updated in zookeeper. |
| Fields inherited from interface com.bigdata.service.jini.master.TaskMaster.ConfigurationOptions |
|---|
AGGREGATORS_TEMPLATE, CLIENTS_TEMPLATE, DELETE_JOB, FORCE_OVERFLOW, INDEX_DUMP_DIR, INDEX_DUMP_NAMESPACE, JOB_NAME, NAGGREGATORS, NCLIENTS, SERVICES_DISCOVERY_TIMEOUT, SERVICES_TEMPLATES |
| Field Detail |
|---|
static final String OPERATION_COUNT
static final String SEED
static final String NAMESPACE
static final String ASYNCHRONOUS
true the client writes will use the asynchronous
API. Otherwise they will use the synchronous RPC API.
static final String NPARTITIONS
static final String START_KEY_PARTITIONS
true, each client is
assigned a key-range when it is created and the client will choose
its startKey for each operations from that key-range. When
false, each client chooses a startKey randomly from
the entire key range for each task. There is no default.
static final String MAX_KEYS_PER_OP
static final String INC_RANGE
This directly controls the maximum distance between keys in a batch operations. In turn, that translates into the "sparsity" of the operation. A small value (~10) can show 4x higher throughput than a value of 1000. This is because the btree cache is more or less being defeated as the spacing between the keys touched in any operation grows.
When incRange is small, the randomly generately keys will be tightly clustered and are likely to be not only within the same index partition by in the same region of the B+Tree on that index partition. As incRange is becomes larger, the keys are more likely to be distributed within a given index partition.
Integer.MAX_VALUE is not sufficient to cause
scattering across index partitions since the range for
Long is so much larger than the range Integer
(it is restricted to Integer by Random.nextInt(int) but
we could find a way to work around that)., update incRange => operations per second (Disk, no sync on
commit, laptop, 5.23.07).
10 463 100 222 1000 132 10000 114 100000 116
static final String ZOOKEEPER_UPDATE_INTERVAL
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||