CreateInsert & ClearInsert benchmarks #33
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.
The benchmarks are kind of similar to
InsertHugeInt
, but stress test different sizes, some maps seem to really struggle after certain sizes:(The above was just a quick average of two benchmark with the timeout set to 100s)
This was the last benchmark I had lying around on my system, but I think an erase-if benchmark is still missing.
I tried implementing one today, but I don't really see a good way of doing it, as creating the map is always way more expensive than the erase-if.
Also, abseil has non-standard iterators, and I'm not sure if all the other maps confirm to the standard implementation.