On 11 Jan 2021, at 9:25, Robert Stepanek wrote: > There are several issues with Xapian currently, the big one being that by default it is *only* used for fuzzy searches. > > Just curious, what issues are you referring to? I was referring to this post from “pendragonsound” in May 2020: > This begs the question of why I simply didn't convert to Xapian, because of its favored status with Fastmail. Early in our upgrade to 3.0.13 I set up a sandbox with a cloned copy of a large mailbox running 3.0.13/Xapian and compared it to 2.5.7/Squat (our operational system at the time). Xapian was far more powerful in terms of search complexity/specificity, but was unbearably slow compared to Squat for simple searches in large mailboxes. Given that a vocal portion of our users searches multiple large mailboxes simultaneously, Xapian was not a workable solution. But this was before I discovered that Squat is also unusable out of the box in 3.0.13. I didn’t actually test that myself. Can you say if Xapian is faster in 3.2 or 3.4, and how it compares to Squat? > On a related note: there is a fix for squat backend search in the works and it looks quite promising. I'll backport it to the 3.4 branch https://github.com/cyrusimap/cyrus-imapd/pull/3316 That’s good to hear. Cheers, Sebastian -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
Attachment:
smime.p7s
Description: S/MIME digital signature
------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/T39b16104c6d0df13-M39e92bd767c203012f816394 Delivery options: https://cyrus.topicbox.com/groups/info/subscription
