[tpayet]

Actually, Meilisearch uses the RAM available by design because it uses LMDB (which is memory-mapped) under the hood for key-value storage.

It's a feature, not a bug :D

The cool thing about that is that it is the OS that will get to choose which process to allocate memory, and you can always run it somewhere with less memory available, and it will work the same way

[yellow_lead]

But is there any way to limit the memory? Sometimes I want to run more than one thing on the box. I found that meilisearch doesn't have a "max total memory use" flag

[irevoire]

Hey, as the previous person said you cannot really limit the memory, Meilisearch uses.

But your OS will share the Meilisearch memory with other process seamlessly, you don’t have anything to do. In htop it’s the yellow bar, and it’s basically a big cache shared between all processes.

[yellow_lead]

I haven't found this to be the case in my experience. Although I may be misunderstanding, but this is my experience running Meili in prod:

* Meili uses 50% RAM

* I use 10-20% with another script to occasionally index new data

* When indexing, Meili could jump to use 70-80% RAM

* Meili is OOM killed

[Kerollmops]

Right. We released a lot of new versions of the engine to improve the indexing part of it. V1.12 is improving the document indexing a lot! Have you tried the latest version v1.14 we released yesterday?

While Meilisearch is capable of limiting it's resident (actual mallocs) memory. However, it requires a bare minimum (about 1GiB).