-
Notifications
You must be signed in to change notification settings - Fork 177
First sketch of MDB_DUPSORT. #5558
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
base: develop
Are you sure you want to change the base?
Conversation
|
I've played a bit with DUPSORT and have the following results:
Peformance with DUPSORT: Performance on develop: |
6f953d9 to
a7fa590
Compare
|
I tested DUPSORT in my branch and implemented it specifically for the SP** index. Seemed to make som small performance improvements, but not sure it was much. |
|
@hmottestad My primary goal is to reduce the DB size on disk. I've also experimented with Morton (Z-oder) codes to only have one index. But this performed bad. |
09b18cf to
d8e4017
Compare
5033f2a to
4b8ec4b
Compare
4b8ec4b to
c815e5d
Compare
5dfe593 to
eabd5ca
Compare
eabd5ca to
83371cb
Compare
GitHub issue resolved: #4218
Briefly describe the changes proposed in this PR:
PR Author Checklist (see the contributor guidelines for more details):
mvn process-resourcesto format from the command line)