I tested Meilisearch last year indexing 10mil documents it took 2 days!
same dataset with the same server specs it took less than 2 hours to index in elasticsearch.
This is great. The only major thing Meilisearch is missing after hybrid search is introduced IMO is high availability. Without clustering, it’s hard to run any meaningful production workloads and there doesn’t seem to be an online upgrades story.
> but we decided to go with RoaringBitmaps to reduce their size<p>Interesting. Could you elaborate on the benefit of this?<p>I've (possibly prematurely) discarded the notion of using RoaringBitmaps like this because while they use less memory, traversal is and mutation is <i>so</i> much slower using a fixed buffer out of a pool and considering an upper bounded slice of putative results at a time.<p>Although this is for a search engine that typically deals with under-specified queries and is designed for best-effort retrieval given an upper computation time.
I'm thinking of putting this for software documentation. The idea is that content is all markdown in Astro or Seveltkit with SSG (static site generation) and then Index it all at build time and then search it all via Meliesearch.