Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove ngram offset code #616

Merged
merged 2 commits into from
Jul 17, 2023
Merged

remove ngram offset code #616

merged 2 commits into from
Jul 17, 2023

Conversation

keegancsmith
Copy link
Member

We have been running btree as the default for many months. We worried about a performance hit, but it never happened. After some recent local testing I did I noticed the btree actually interacted with the disk more efficiently. So the old code both uses more memory and is slower, lets just remove it.

Test Plan: go test ./...

We have been running btree as the default for many months. We worried
about a performance hit, but it never happened. After some recent local
testing I did I noticed the btree actually interacted with the disk more
efficiently. So the old code both uses more memory and is slower, lets
just remove it.

Test Plan: go test ./...
This is no longer needed, we always use the btree. Additionally I added
some documentation.
@keegancsmith keegancsmith requested a review from a team July 14, 2023 19:30
@keegancsmith keegancsmith merged commit 3d0bdd5 into main Jul 17, 2023
8 checks passed
@keegancsmith keegancsmith deleted the k/rm-combined branch July 17, 2023 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants