Add min parallelism and fix the build #89
Merged
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.
There are workloads which require more vertical scaling due to required parallelism, so now the planner can take read and write parallelism into account.
For example, imagine that a Java process creates 4 concurrent futures in response to a read request, then it needs at least 4 cores for that workload to run in parallel (as opposed to concurrent). The defaults are 1+1 for read+write which means our minimum instance size is effectively 2 cores. Given that hyperthreading is the default for most AWS instances this is reasonable.
Python 3.7 is EOL so remove testing that and add in Python 3.10.