While I really liked the neat API and it's easy to use, the index performance and ram/disk size is really disappointing in a use case I oversee.
Typesense in my opinion is much better on performance (ymmv but in my case it's ~15% disk/ram, 5% of index time comparing to Meili). However, it's a bit behind on easy to use: the auto schema api has some limitation, also lack of official arm64 build (maybe it's a c++ vs rust toolchain thing, it takes quite some time to compile by oneself, with many c++ libs used from different vendors like google/baidu/etc, and some lib even requires SSE)
It's fun to see both come with comparison charts [1] [2], I dunno who started this but competition is good for the industry (except I'm mildly concerned GitHub stars are used in PR like this), and I hope both get better over time.
This is Kishore, co-founder of Typesense. We will be publishing an ARM64 build from the next release. And I hear you about the auto schema: working on that as well.
Typesense in my opinion is much better on performance (ymmv but in my case it's ~15% disk/ram, 5% of index time comparing to Meili). However, it's a bit behind on easy to use: the auto schema api has some limitation, also lack of official arm64 build (maybe it's a c++ vs rust toolchain thing, it takes quite some time to compile by oneself, with many c++ libs used from different vendors like google/baidu/etc, and some lib even requires SSE)
It's fun to see both come with comparison charts [1] [2], I dunno who started this but competition is good for the industry (except I'm mildly concerned GitHub stars are used in PR like this), and I hope both get better over time.
[1] https://docs.meilisearch.com/learn/what_is_meilisearch/compa...
[2] https://typesense.org/docs/overview/comparison-with-alternat...