go: Optimize some SELECTs against dolt_log for some types of databases.#10592
Merged
go: Optimize some SELECTs against dolt_log for some types of databases.#10592
dolt_log for some types of databases.#10592Conversation
…sage to not fully resolve tags.
…onfigurable with the DOLT_COMMIT_CACHE_SIZE env var.
Contributor
Contributor
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
3 participants
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.
Databases with lots of tags will see a performance improvement on analyzing queries which use
dolt_log.An internal cache has been increased in size. Database servers which regularly run queries against
dolt_logwhich visit more than 10,000 commits will be able to take advantage of the larger cache and will see the performance of those queries improve.