Adds benchmarks for insertion/operations/lookup #90
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.
This PR add benchmarks for insertion, operations and lookups. For now, I have only implemented them for the map types, my reasoning being that the set types are rather small wrappers around those and as such, measuring the performance of the map types should be sufficient.
The benchmarks are configurable using constants. You can set these to different values and observe how the code performs. The available constants are:
Key
: key types being usedValue
: value types being usedCOUNT
: count for the insertionsOPERATIONS
: number of operationsLOOKUPS
: number of lookupsThe benchmark is also set to calculate throughput, such as to have a better understanding of the the times mean. Note that the rangemap likely scales
O(n log n)
, so that changing the insertions/operations/lookups affects the measured throughput (in other words, the throughput does not stay constant).I have used
proptest
to generate the input sets here, simply because it is convenient.