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

Database maintenance: compacting #223

Open
dilyanpalauzov opened this issue Feb 28, 2022 · 0 comments
Open

Database maintenance: compacting #223

dilyanpalauzov opened this issue Feb 28, 2022 · 0 comments

Comments

@dilyanpalauzov
Copy link

Cyrus-IMAP uses Xapian, too. It feeds new email into a Xapian database. Over time, the Xapian database gets pretty big and each change tooks longer and longer. The recommendation is to do regularly “database compaction (repack)”. The old data is compressed into a smaller database, new data goes into a recently created database. The recently created database is small, thus adding data to it and saving the changes is also fast. On search, both the new and old, compacted databases are used.

In the documentation of xapian-haystack I do not find any text about this compaction and having many database files (tiers), used simultaneously when searching.

https://lists.tartarus.org/pipermail/xapian-discuss/2014-October/009112.html

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

No branches or pull requests

1 participant