4 ms·

typesense did their own comparison here: https://typesense.org/typesense-vs-algolia-vs-elasticsearch-vs-meilisearch/ https://typesense.org/typesense-vs-algolia

typesense did their own comparison here: https://typesense.org/typesense-vs-algolia-vs-elasticsearch-vs-meilisearch/ https://typesense.org/typesense-vs-algolia-vs-elasticsearch-...

deleted 4y ago
[deleted]
curquiza 4y ago
Unfortunately, the comparison with Meilisearch is not up to date in this link. Also, we have to keep in mind that every comparison written by a company is always oriented.
- jabo 4y ago
  I maintain that comparison page on the Typesense side. I just updated it as recently as yesterday, based on my observation. But let me know which ones need updating for Meilisearch. Happy to update. While we’re on the topic, reminder about some of the outdated information in your comparison pages: https://twitter.com/typesense/status/1620825236055932928?s=46&t=ryPI1ZnQYEvrXgPmPl9I5Q https://twitter.com/typesense/status/1620825236055932928?s=4...
  - traverseda 4y ago
    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 useful for the type of stuff I'm doing: https://docs.meilisearch.com/learn/what_is_meilisearch/comparison_to_alternatives.html https://docs.meilisearch.com/learn/what_is_meilisearch/compa... Of course I'm not a large enterprise e-commerce site. I'm doing personal projects like web archiving, (dataset probably won't be anywhere near fitting in ram) or I'm using search engines on embedded devices (search needs to play well with others, not use all my ram).
    - jabo 4y ago
      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=34708658 https://news.ycombinator.com/item?id=34708658
      - traverseda 4y ago
        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-feature. The whole things just sounds biased in a way that the meilisearch comparison doesn't. There are some killer features in typesense for sure, just my first impression of it is that it's very much aimed at someone other than me. >Typesense follows a memory model similar to Redis The difference is that redis is primarily being used as a cache, or for IPC, or as a task-queue. You're not loading a whole bunch of data into, and you expect that the data you have in it will either be short-lived (IPC, queue) or can be evicted with no issues (caching).
        jabo 4y ago
        > 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 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.
  - curquiza 4y ago
    We sent mails but we got no updates on them.
    - jabo 4y ago
      Hmmm, I remember those emails and I did reply to gmourier, and made almost all of the changes he pointed out, to our comparison page. Here's [1] the exact commit with the changes I made. The only one change I didn't make is the one about Meilisearch not being constrained by RAM, because of reports like this [2] I've seen in the past and because I saw this in your docs: https://docs.meilisearch.com/learn/advanced/storage.html#memory-mapping https://docs.meilisearch.com/learn/advanced/storage.html#mem... >For the best performance, it is recommended to provide the same amount of RAM as the size the database takes on disk, so all the data structures can fit in memory. [1] https://github.com/typesense/typesense-website/commit/0103ff484d68b1c8556f61c876cadf1480dde720 https://github.com/typesense/typesense-website/commit/0103ff... [2] https://news.ycombinator.com/item?id=34708658 https://news.ycombinator.com/item?id=34708658 Let me know which other ones need updating.

typesense did their own comparison here: https://typesense.org/typesense-vs-algolia-vs-elasticsearch-vs-meilisearch/ https://typesense.org/typesense-vs-algolia-vs-elasticsearch-...

deleted 4y ago

[deleted]

curquiza 4y ago

Unfortunately, the comparison with Meilisearch is not up to date in this link. Also, we have to keep in mind that every comparison written by a company is always oriented.

jabo 4y ago
I maintain that comparison page on the Typesense side. I just updated it as recently as yesterday, based on my observation. But let me know which ones need updating for Meilisearch. Happy to update. While we’re on the topic, reminder about some of the outdated information in your comparison pages: https://twitter.com/typesense/status/1620825236055932928?s=46&t=ryPI1ZnQYEvrXgPmPl9I5Q https://twitter.com/typesense/status/1620825236055932928?s=4...
- traverseda 4y ago
  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 useful for the type of stuff I'm doing: https://docs.meilisearch.com/learn/what_is_meilisearch/comparison_to_alternatives.html https://docs.meilisearch.com/learn/what_is_meilisearch/compa... Of course I'm not a large enterprise e-commerce site. I'm doing personal projects like web archiving, (dataset probably won't be anywhere near fitting in ram) or I'm using search engines on embedded devices (search needs to play well with others, not use all my ram).
  - jabo 4y ago
    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=34708658 https://news.ycombinator.com/item?id=34708658
    - traverseda 4y ago
      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-feature. The whole things just sounds biased in a way that the meilisearch comparison doesn't. There are some killer features in typesense for sure, just my first impression of it is that it's very much aimed at someone other than me. >Typesense follows a memory model similar to Redis The difference is that redis is primarily being used as a cache, or for IPC, or as a task-queue. You're not loading a whole bunch of data into, and you expect that the data you have in it will either be short-lived (IPC, queue) or can be evicted with no issues (caching).
      - jabo 4y ago
        > 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 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.
- curquiza 4y ago
  We sent mails but we got no updates on them.
  - jabo 4y ago
    Hmmm, I remember those emails and I did reply to gmourier, and made almost all of the changes he pointed out, to our comparison page. Here's [1] the exact commit with the changes I made. The only one change I didn't make is the one about Meilisearch not being constrained by RAM, because of reports like this [2] I've seen in the past and because I saw this in your docs: https://docs.meilisearch.com/learn/advanced/storage.html#memory-mapping https://docs.meilisearch.com/learn/advanced/storage.html#mem... >For the best performance, it is recommended to provide the same amount of RAM as the size the database takes on disk, so all the data structures can fit in memory. [1] https://github.com/typesense/typesense-website/commit/0103ff484d68b1c8556f61c876cadf1480dde720 https://github.com/typesense/typesense-website/commit/0103ff... [2] https://news.ycombinator.com/item?id=34708658 https://news.ycombinator.com/item?id=34708658 Let me know which other ones need updating.