←back to thread

Meilisearch – search engine API bringing AI-powered hybrid search

(github.com)
151 points modinfo | 1 comments | 14 Apr 25 12:46 UTC | HN request time: 0.241s | source
Show context
be_erik ◴[14 Apr 25 14:00 UTC] No.43681389[source]▶
Is meilisearch ready for production workloads? I would love to use some of the feature set, but is the only option for HA running multiple instances and keeping them in sync?
replies(4): >>43681438 #>>43681696 #>>43681927 #>>43682137 #
bigtones ◴[14 Apr 25 15:07 UTC] No.43682137[source]▶
We use Meilisearch in production with a 7 million article corpus - it works really well.
replies(1): >>43682729 #
iambateman ◴[14 Apr 25 15:58 UTC] No.43682729[source]▶
My understanding for Meilisearch is that you need enough RAM to keep everything in memory...but you're (probably) not keeping full-text in memory for millions of articles.

Is it just searching metadata, or do you just have a setup that's beefy enough to support that level of memory?

Or am I just wrong? :D

replies(3): >>43682783 #>>43687676 #>>43689680 #
1. tpayet ◴[14 Apr 25 16:02 UTC] No.43682783[source]▶
Meilisearch keeps all the data on disk. It uses memory-mapping for optimizing performance, by default everything is safe on disk and the OS cache the most needed pages in memory.

So it works on any machine, really. 2GiB is usually enough for most workloads, but the bigger the dataset, the faster it will be if you give it more memory!