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

Consider improvements on many copies of message indexes in leveldb implementation #631

Open
thehenrytsai opened this issue Nov 28, 2023 · 0 comments
Labels
performance performance improvement

Comments

@thehenrytsai
Copy link
Member

Currently a full copy of the record indexes is stored for every index table. There are ~20 indexed properties for a record, this means the same ~20 indexed key-value pairs are stored 20 times.

We should investigate to see if there are ways to improve storage usage without sacrificing performance too much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance performance improvement
Projects
None yet
Development

No branches or pull requests

1 participant