Skip to content
This repository
tree: 3827d9a303

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 conf
Octocat-spinner-32 src
Octocat-spinner-32 README
Octocat-spinner-32 pom.xml

YCSB_HOME - YCSB home directory
DYNAMODB_HOME - Amazon DynamoDB package files


$YCSB_HOME/bin/ycsb load dynamodb -P worklaods/workloada -P
$YCSB_HOME/bin/ycsb run dynamodb -P worklaods/workloada -P



* Why is the recommended workload distribution set to 'uniform'?
    This is to conform with the best practices for using DynamoDB - uniform,
evenly distributed workload is the recommended pattern for scaling and
getting predictable performance out of DynamoDB

For more information refer to

* How does workload size affect provisioned throughput?
    The default payload size requires double the provisioned throughput to execute
the workload. This translates to double the provisioned throughput cost for testing. 
The default item size in YCSB are 1000 bytes plus metadata overhead, which makes the 
item exceed 1024 bytes. DynamoDB charges one capacity unit per 1024 bytes for read 
or writes. An item that is greater than 1024 bytes but less than or equal to 2048 bytes 
would cost 2 capacity units. With the change in payload size, each request would cost 
1 capacity unit as opposed to 2, saving the cost of running the benchmark. 

For more information refer to

* How do you know if DynamoDB throttling is affecting benchmarking?
    Monitor CloudWatch for ThrottledRequests and if ThrottledRequests is greater
than zero, either increase the DynamoDB table provisioned throughput or reduce
YCSB throughput by reducing YCSB target throughput, adjusting the number of YCSB
client threads, or combination of both.

For more information please refer to

When requests are throttled, latency measurements by YCSB can increase.

Please refer to for more information.

Please refer to Amazon DynamoDB docs here:
Something went wrong with that request. Please try again.