Congrats team. Meilisearch is an absolute joy to work with.
Thanks!
Meilisearch 1.0 – Open-source search engine built in Rust
81–90 of 186 posts
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#82Earlier quoted context omitted.
I'd say that the bit where typesense can only work with data that fits in ram is actually a pretty big problem for a lot of use cases, as an aside. That feature alone would discount typesense for basically all of my personal projects. Might be a trade off I'd be willing to make on a professional project given the other features but it seems really wasteful. Personally I find the meilisearch comparison to be more usef…
That is also MeiliSearch's recommended setup though: > For the best performance, it is recommended to provide the same amount of RAM as the size the database takes on disk https://docs.meilisearch.com/learn/advanced/storage.html#lmd...
There's a big difference between recommended and required. Of course things work better if your entire dataset fits in ram, and of course at the giant enterprise scale you can do that, but it's not something I'm going to do on my VPS along side wordpress, you know? I don't really care about getting maximum possible performance when the data is only going to be accessed intermittently. I care about letting the OS maximize performance by choosing what gets cached in ram.
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#83Is Rust that important that you have to place "built in Rust" in the title? Is this like a cult following that we only bet on traffic and interest coming from other evangelists where Rust is the only feature that matter? 4 months ago: " Meilisearch, open-source alternative to Algolia in Rust lands a $15M Series A" It's not the first time I see, there are at least 2-3 daily submissions reaching the FP in this manner s…
> cult following
Seems unnecessary to jump right to cult following. Not "cult" but RSS following is often the case where keyword in title makes the difference. I wonder why does it bothers you if it is not relevant for you. What is your problem? Why can people let others be?
> It's not the first time I see
Obviously and your comment is not first complaining about that title contains "implemented in X".
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#84Earlier quoted context omitted.
Typesense follows a memory model similar to Redis - you need sufficient RAM to hold the entire dataset. I don't want to speak for the Meilisearch team, but from observing user reports like this [1], it seems to me like you'd need at least X-2X RAM to run Meilisearch, if X is the size of your dataset, if you want it to not slow down as it swaps content from Disk to RAM. [1] https://news.ycombinator.com/item?id=3470865…
I mean that user report is from me, and was about a very very early meilisearch version. Maybe wrong link? > if you want it to not slow down as it swaps content from Disk to RAM. Obviously it's going to be fastest to run with your entire dataset in RAM, that's never in doubt. Part of why I find the whole typesense comparison page disingenuous is that you're making the ability to swap to disk sound like an anti-featur…
> Part of why I find the whole typesense comparison page disingenuous is that you're making the ability to swap to disk sound like an anti-feature.
Didn’t intend it that way. In fact, we recommend that users configure swap space even in Typesense as a safety mechanism.
May I know which part of the comparison table makes it sound like that?
The one under Index location says: “Disk with Memory Mapped files” for Meilisearch, which I updated based on the Meilisearch team’s feedback…
Edit: To your first point, I meant to link to the parent comment: https://news.ycombinator.com/item?id=34708352
I’ve also seen similar RAM recommendations from the Meilisearch team on GitHub to other users reporting similar performance issues.
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#85My team tried to use Meilisearch for large datasets, unfortunately, it's impossible to plan the RAM usage. If you have very little searches, it consumed very little, but if you have a lot of search traffic, it may consume more than we could provision beforehand. This made it too unpredictable and too expensive, so we went with Manticore instead. I don't know if this has been addressed in 1.0, hopefully it has.
How is the startup time?
Would be nice if you could check a query and then start the instance with an appropriate memory configuration.
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#86My team tried to use Meilisearch for large datasets, unfortunately, it's impossible to plan the RAM usage. If you have very little searches, it consumed very little, but if you have a lot of search traffic, it may consume more than we could provision beforehand. This made it too unpredictable and too expensive, so we went with Manticore instead. I don't know if this has been addressed in 1.0, hopefully it has.
How is the startup time? Would be nice if you could check a query and then start the instance with an appropriate memory configuration.
Pretty much instant, it loads data from a memory-mapped file so having a fast SSD for that is a must.
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#87Earlier quoted context omitted.
As some people mentioned: I generally expect a higher standard of software when I see "build in Rust". That expectation includes a few things such as stability and operational UX (ie how easy it is to run and maintain). And these (in my experience as a Rust developer) stems from the fact that it's much easier to get the MVP and business logic taken care of becau I'm not bogged down by the drudgery of menial tasks tha…
While I can agree on the argument that rust offer many ergonomics and keep us away on many classes of security and memory management related issues. The quality of UX/DX is more defined by product and design requirements, not much to do with language of choice. Similar like restful api, good or bad is on the designer hand most of the time, not because it's implemented on some esoteric language.
Yeah, but there's usually more time to put an emphasis on UX, as well as the fact that the ergonomics of the language again make it easier to implement the UX.
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#88What language you write a program in is not a feature, definitely not a headline one.
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#89What language you write a program in is not a feature, definitely not a headline one.
Maybe not for you. But for my RSS filter it definitely is.
Re: Meilisearch 1.0 – Open-source search engine built in Rust
#90Is Rust that important that you have to place "built in Rust" in the title? Is this like a cult following that we only bet on traffic and interest coming from other evangelists where Rust is the only feature that matter? 4 months ago: " Meilisearch, open-source alternative to Algolia in Rust lands a $15M Series A" It's not the first time I see, there are at least 2-3 daily submissions reaching the FP in this manner s…
When I see built in Rust I know the software is well built, easy to further extend if it is open source, and probably won't crash or bug out on me.