Meilisearch – search engine API bringing AI-powered hybrid search

(github.com)

151 points modinfo | 2 comments | 14 Apr 25 12:46 UTC | HN request time: 2.396s | source

Show context

saintfiends ◴[14 Apr 25 17:49 UTC] No.43684092[source]▶

Meilisearch is really good for a corpus that rarely changes from my experience so far. If the documents frequently change and you have a need to have those changes available in search results fairly quickly it ends up with pending tasks for hours.

I don't have a good solution for this use-case other than maybe just the good old RDBMS. I'm open for suggestions or anyway to tweak Meilisearch for documents that gets updated every few seconds. We have about 7 million documents that's about 5kb each. What kind of instance do I need to handle this.

replies(2): >>43684299 #>>43686465 #

1. brandonlovesked ◴[14 Apr 25 21:23 UTC] No.43686465[source]▶

>>43684092 #

You have 35gib of data, put it in memory and forget about nvmes and hdds

replies(1): >>43686567 #

2. Kerollmops ◴[14 Apr 25 21:33 UTC] No.43686567[source]▶

>>43686465 (TP) #

35 GiB is probably a third of the data I index into Meilisearch just for experimenting and don't forget about the inverted indexes. You wouldn't use any O(n) algorithm to search in your documents.

Also, every time you need to reboot the engine you would have to reindex everything from scratch. Not a good strategy, believe me.

↑