HackerTrans
TopNewTrendsCommentsPastAskShowJobs

qdequelen

no profile record

Submissions

Building a Rust-based DiskANN on top of LMDB

github.com
1 points·by qdequelen·há 3 anos·0 comments

Get in-product UX insights with Maze

maze.co
2 points·by qdequelen·há 3 anos·0 comments

comments

qdequelen
·há 2 anos·discuss
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 raw data on our cloud, and it scales amazingly well. https://x.com/Kerollmops/status/1772575242885484864
qdequelen
·há 2 anos·discuss
> 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.
qdequelen
·há 2 anos·discuss
Thanks for the highlight!
qdequelen
·há 3 anos·discuss
Do you handle high throughput volumes? I would need this for testing to host a database service at scale.
qdequelen
·há 3 anos·discuss
Did you only get the schema.json?
qdequelen
·há 3 anos·discuss
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!
qdequelen
·há 3 anos·discuss
Thanks @CaroFG, I'm sure that if anyone has questions, the engineering team would love to answer!
qdequelen
·há 3 anos·discuss
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/1000 documents and searches. And, funny thing, we are thinking about splitting the searches and documents, too, but we wanted to have more data to be sure to select the right unit price for each. :)
qdequelen
·há 3 anos·discuss
Make the web faster with Rust.
qdequelen
·há 3 anos·discuss
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 Meilisearch and Typesense are really different regarding resource consumption and performance. I would say that where Typesense would have a better indexing performance (Meilisearch has recently improved indexation speed), Meilisearch will guarantee a much faster search performance while keeping impressive relevancy. Regarding the consumption, as Typesense is entirely on RAM and Meilisearch is using memory mapping, Meilisearch would take more disk space but less RAM.
qdequelen
·há 3 anos·discuss
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.
qdequelen
·há 3 anos·discuss
Thanks for your feedback!
qdequelen
·há 3 anos·discuss
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.
qdequelen
·há 3 anos·discuss
Yes, it's planned!
qdequelen
·há 3 anos·discuss
Yes, indeed, it's crucial to have an SSD. With it, loading will be instant (a few ms).
qdequelen
·há 3 anos·discuss
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 uses memory-mapping, which means that everything is on disk, and it will try to take as much memory as possible. For your information, we successfully ran a 115M documents dataset on a 1Gb RAM machine.