qdequelen

8 ms·

1. 1.▲
   by qdequelen 2y ago

   Hey PSeitz, Meilisearch CEO here. Sorry to hear that you failed to index a low volume of data. When did you last try Meilisearch? We have made significant improvements in the indexing speed. We have a customer with hundreds of gigabytes of
2. 2.▲
   by qdequelen 3y ago

   > Are LLM tools better or worse than e.g. meilisearch or elasticsearch for searching with snippets over a set of document resources? Absolutely worse, LLM are not made for it at all.
3. 3.▲
   by qdequelen 3y ago

   Thanks for the highlight!
4. 4.▲
   Building a Rust-based DiskANN on top of LMDB(github.com)

   1 points by qdequelen 3y ago|0 comments
5. 5.▲
   by qdequelen 3y ago

   Do you handle high throughput volumes? I would need this for testing to host a database service at scale.
6. 6.▲
   by qdequelen 3y ago

   Did you only get the schema.json?
7. 7.▲
   by qdequelen 3y ago

   Hey, I'm the CEO of Meilisearch. If your issue is performance, I would love to give you a try with Meilisearch. You'll be able to create an "as you type" experience with our engine that responds in less than 50ms!
8. 8.▲
   by qdequelen 3y ago

   Thanks @CaroFG, I'm sure that if anyone has questions, the engineering team would love to answer!
9. 9.▲
   by qdequelen 3y ago

   Hello, I'm the Meilisearch CEO. I think you're also correct, Jabo. I just want to clarify. Meilisearch's pricing doesn't start at 1.2K/month, but at 0/month. We have a usage-based pricing that is basically 0.25
10. 10.▲
    by qdequelen 4y ago

    Make the web faster with Rust.
11. 11.▲
    by qdequelen 4y ago

    Hey muhammadusman, I'm the Meilisearch's CEO. We have a complete comparison table. Note that it represents our point of view. https://docs.meilisearch.com/learn/what_is_meilisearch/compa... Both Meilisea
12. 12.▲
    by qdequelen 4y ago

    To answer your question precisely, we handle all the space-separated languages and have specific tokenizers for Chinese, Japanese, Korean, Thai, and Hebrew. We plan to add more languages in the future.
13. 13.▲
    by qdequelen 4y ago

    Thanks for your feedback!
14. 14.▲
    by qdequelen 4y ago

    You should try it again since we intensively improved the indexation performances. Most of our actual users no longer have performance problems, even on hundreds of millions of documents.
15. 15.▲
    by qdequelen 4y ago

    Yes, it's planned!
16. 16.▲
    by qdequelen 4y ago

    Yes, indeed, it's crucial to have an SSD. With it, loading will be instant (a few ms).
17. 17.▲
    by qdequelen 4y ago

    You should definitely try Meilisearch again. We have optimized a lot of the consumption and indexation performance. Even with all the improvements, we think it's essential to continue focusing on it during 2023. And indeed, Meilisearch
18. 18.▲
    Get in-product UX insights with Maze(maze.co)

    2 points by qdequelen 4y ago|0 comments
19. 19.▲
    Improve your support productivity with Crisp and GPT-3 MagicReply feature(crisp.chat)

    1 points by qdequelen 4y ago|0 comments
20. 20.▲
    by qdequelen 4y ago

    If you remove the URLs from indexation, it'll generally save a ton of place and will be much, much faster to index. We are thinking about not indexing URLs by default; you can help us by explaining your use case here -> https:&#x2F
21. 21.▲
    by qdequelen 4y ago

    Hello, I'm the Meilisearch CEO, your issues could be because you sent your data without configuring your index, and it's what I read from your comment. Just change your setting to not index URLs. Check out the doc: https:/&#
22. 22.▲
    by qdequelen 4y ago

    Can I get your use case? What is the data you have to index? If it's logs, indeed, Meilisearch will not be the best fit. I would recommend https://quickwit.io . If it's structured or unstructured data, even if 10TB seem
23. 23.▲
    by qdequelen 4y ago

    Hello, I would love to know what are your needs/limitations that makes you ask for cluster/sharding. Meilisearch is cloud-native, so we don't need clusters of machines to provide a highly available solution. By default, our s
24. 24.▲
    by qdequelen 4y ago

    Cool! Meilisearch's CEO here. We have spent so much time improving indexation speed. I'm so glad the experience is better for you now! Even more improvements will be released in the future.
25. 25.▲
    by qdequelen 4y ago

    Good to know. If you find some Russian language support improvement we can do, don't hesitate to create an issue on our tokeniser https://github.com/meilisearch/charabia . Moreover, it's Hacktoberfest. If you
26. 26.▲
    by qdequelen 4y ago

    Hello, I'm Quentin, Meilisearch's CEO. Meilisearch Cloud is encrypted at rest. We're using, at this time, a k8s with replicated and encrypted persistent volumes. We just didn't talk about it yet.
27. 27.▲
    by qdequelen 4y ago

    Thanks! Happy to get you as a user :)
28. 28.▲
    by qdequelen 4y ago

    Hello everyone, I'm Quentin, the CEO of Meilisearch. We are very proud to announce today our incredible fundraising. Over the last three years, we have succeeded in establishing ourselves as a serious competitor in the search industry
29. 29.▲
    Open-source can drive a company strategy(blog.meilisearch.com)

    10 points by qdequelen 4y ago|0 comments
30. 30.▲
    by qdequelen 5y ago

    Indeed for the moment, I would not advise going to more than a few million documents, especially if you want to make regular updates. With the new update that we will release in March, I think we will go up to a few tens of millions of docu