Use only valid characters for benchmarking #73
Closed
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.
I just hardcoded the valid chars in benchmarks and now the benchmarks seem to make some sense. However, I cannot explain why the benchmarks were 400 us when we used the full range and now they are in milliseconds. Were we erroring out or something on encountering the first invalid char?
Old results with full range including invalid chars:
New results with only valid char blocks: