opst index range not returning correct results, perf improve #285
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zonotope
approved these changes
Dec 2, 2022
| m' (or m (if (identical? >= test) util/min-integer util/max-integer))] | ||
| (flake/create s' p o' dt t op m')))) | ||
| [test s p o t op m] | ||
| (let [[o' dt] (if (vector? o) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
opst range calls were not producing accurate results under certain circumstances
While looking at index-range, there were two blocking async calls that were frequently not needed. By making them only perform the async ops when needed it reduced time required for small lookups from an average of > 100µs to ~80µs.
The code is slightly less pretty, but given this is the most common operation we perform a 20% speed boost is welcome.