Fix read capacity calculation and wait between scans #63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #60
The current implementation of the usable read capacity has some issues and might lead to provisioned throughput exceptions.
The current implementation has two problems:
The new implementation solves these issues and will no longer exceed the requested limit. Exceptions to this case are tables that have a very low provisioned read capacity (e.g. 1), where the percentage limit has little effect and will result in an average consumption of 1 read capacity.
Backups might now take longer, but at least they respect the given read capacity.