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

add a tiered merge policy #114

Merged
merged 8 commits into from Mar 3, 2019

Conversation

Projects
None yet
2 participants
@hendrikmuhs
Copy link
Contributor

hendrikmuhs commented Feb 21, 2019

The tiered merge policy is a smarter selection algorithm for selecting segments to merge. It scores sets of segments while prefering similar sized segments while boosting smaller merges and segments with deletes.

The algorithm is inspired by Lucene's tiered merge policy.

This change makes the tiered merge policy the default

@hendrikmuhs hendrikmuhs added the wip label Feb 21, 2019

@coveralls

This comment has been minimized.

Copy link

coveralls commented Feb 22, 2019

Coverage Status

Coverage increased (+0.1%) to 94.985% when pulling bad4942 on hendrikmuhs:tiered-merge into 038f1f3 on KeyviDev:master.

hendrikmuhs added some commits Feb 23, 2019

@hendrikmuhs hendrikmuhs removed the wip label Feb 26, 2019

@hendrikmuhs

This comment has been minimized.

Copy link
Contributor Author

hendrikmuhs commented Mar 1, 2019

tested this on a larger scale now: > 400 million keys (on my laptop), looks very promising.

@hendrikmuhs hendrikmuhs merged commit f27619a into KeyviDev:master Mar 3, 2019

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage increased (+0.1%) to 94.985%
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.