Tweak lookup Strategy to prioritize the table when its in memory#545
Open
Tweak lookup Strategy to prioritize the table when its in memory#545
Conversation
Prioritize table based lookups (RECORD AND FIELD) if they are in memory before using an INDEX for a conditonKey or orderKey. Even though the index would need to be loaded anyway, performing a lookup using the index is slower than using the table. So, if the table is in memory it should be used because the cache lookup to retrieve the table is the same as the cache lookup to retrieve the index
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.