replayParallelism should be configurable

[nefilim]

this variable has a major impact on performance and consumed capacity in a system with a large amount of persistent actors and should be adjustable.

[sclasen]

+1, PR? should be straightforward.

[neowulf]

Should maxDynamoBatchGet be configurable as well?

It's not clear as to how to constrain the following three variables to the DynamoDB table's provisioned throughput (readCapacityUnits, writeCapacityUnits). For example, during the development process, I want to work with a dynamodb table with read / write capacity units to be as low as 10 (first tier of pricing constraints (pricing)).

• maxDynamoBatchGet
• replayParallelism
• sequence-shards (application.conf)

[sclasen]

maxDynamoBatchGet is basically a const, 100 is the ceiling on number of keys in a batch get.

for dev, you can usually get away with low capacity, as long as your dataset is small of course. If you exceed your capacity calls should back off, and eventually succeed.