5 ms·
Any advantages over Elasticsearch? EDIT: I did read the article, though I overlooked the link to comparison with Elasticsearch.
by artembugara 6y ago
Any advantages over Elasticsearch?
EDIT: I did read the article, though I overlooked the link to comparison with Elasticsearch.
- vvangemert 6y agoDid you even read the article? There's a link in there whith benchmarks it against elasticsearch. Read the conclusion on: https://redislabs.com/blog/search-benchmarking-redisearch-vs-elasticsearch/ https://redislabs.com/blog/search-benchmarking-redisearch-vs...
- sam_lowry_ 6y agoElastic search adds a huge overhead over Lucene. I suspect the same is true for RediSearch. The test is not testing the engine, but rather the implementation of its distributed aspect.
- k_bx 6y agoBut RediSearch is not based on Lucene (as claimed here https://redislabs.com/blog/search-benchmarking-redisearch-vs-elasticsearch/ https://redislabs.com/blog/search-benchmarking-redisearch-vs... )
- sam_lowry_ 6y agoOf course. What I mean is that the performance of distributed FTS is mostly related to its distributed aspect, not FTS by itself. If I were @aphyr, I would say that performance and correctness are competing, so a more performant distributed system is less correct, unless proved otherwise.
- murkt 6y ago> I would say that performance and correctness are competing What an interesting way to look at performance.
- sam_lowry_ 6y ago@murkt That's how I look at the performance benchmarks of distributed systems.
- elric 6y agoCAP theorem is a little bit more nuanced than "more performance is less correct", but I see what you're saying.
- deleted 6y ago[deleted]
- bryanrasmussen 6y agoI mean speed is nice, but it is not the primary thing I am concerned with in a search engine, as long as it is acceptable it is not in the list of requirements - things that would be on my list - not necessarily in this order but close 1. What human languages does it support. 2. In these human languages how does stemming and decompounding work in your implementation. 3. how is word importance determined in your index - TF-IDF? other algorithm? Are least important words automatically dropped from queries? 4. Do you have ability to rank on both the stemmed/decompounded query/results and exact matches? So something like raw field access. 5. Can I create my own semantics - I remember seeing a post on here recently where someone had created a search engine (in Rust I think) that was faster than ElasticSearch but from what I could see you couldn't create your own field names so you were stuck searching in title, description, body, creationDate and a couple other fields which really decreases the usefulness. I mean these are the things that right away spring to mind to ask about when someone tells me they have a new search engine, and when they show me look at my speed benchmarks I'm thinking "what am I supposed to do with this?" on edit: formatting on second edit: So I guess as in most things I am interested in how the product actually fulfills what should be its primary functionality, so how does the search engine function as a search engine, I suppose my questions could be answered with quick - our search engine has feature parity with ElasticSearch / Solr where features A, B, and C are concerned - features D and E will be supported in the future.
- gkorland 6y agoThe question in general is "Yes, RediSearch supports all of these features". You can read about it all in the docs https://redisearch.io https://redisearch.io I also pointed bellow to the specific relevant area in the docs. > 1. What human languages does it support. > 2. In these human languages how does stemming and decompounding work in your implementation. https://oss.redislabs.com/redisearch/Stemming/ https://oss.redislabs.com/redisearch/Stemming/ > 3. how is word importance determined in your index - TF-IDF? other algorithm? Are least important words automatically dropped from queries? >4. Do you have ability to rank on both the stemmed/decompounded query/results and exact matches? So something like raw field access. https://oss.redislabs.com/redisearch/Overview/ https://oss.redislabs.com/redisearch/Overview/
- artembugara 6y agoI missed the link lol
- raziel2p 6y agoThat link is really well hidden in the article IMO. I read your comment and re-read the article and still had to ctrl+F to find it. (It's the 4th link under "blog posts")
- saberience 6y agoYou mean (SHOCK!) that the company that sells Redis thinks their product is better than a competitor!? Color me shocked! I'd like to see actual independent feature and performance comparisons before I come to any actual conclusions.
- softwaredoug 6y agoColor me skeptical anytime a company benchmarks their product against the competition.
- tarjei 6y agoOne of the things I find so confusing with Elasticsearch is querying. Constructing a complex JSON document for a simple query just doesn't fit my brain. I have tried to put this down to bad/confusing documentation, but I'm not sure anymore. It seems Redis is moving a bit in the same direction - although not as complex as ES has done it. Being able to run this inside a Redis instance is a big win, although I suspect few/none of the cloudproviders are willing to pay RedisLabs for the privelige of using the module.
- heipei 6y agoFor my standard use-cases using the query_string query is "good enough", it is the only thing I regularly implement and expose to users. That + some pre-defined aggregations gets you very far. Query String Query can do things like boolean operations (AND, OR, NOT), phrase search, fuzzy search, range search, date math, regex search, boosting: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html https://www.elastic.co/guide/en/elasticsearch/reference/curr...
- gkorland 6y agoRediSearch is available on all the big clouds as a managed solution
- compsciphd 6y agohttps://azure.microsoft.com/en-us/blog/microsoft-and-redis-labs-collaborate-to-give-developers-new-azure-cache-for-redis-capabilities/ https://azure.microsoft.com/en-us/blog/microsoft-and-redis-l...
- mring33621 6y agoAgreed. The JSON query syntax is nonsensical. I much prefer the simpler Lucene style syntax.
- StavrosK 6y agoI've recently started using MeiliSearch and quite like it, does anyone have experience with it?
- logicalmike 6y agoI'm just getting ready to push instant search as a major feature on a client's web application, as both public-facing & admin-side. The MeiliSearch team has been great in terms of communication regarding issues, new features, the roadmap, etc. They're also moving quickly, constantly adding new functionality that has been useful as I've been working on the integration. Depending on what you're planning on using it for, make sure to review the documentation, and check the GitHub issues/discussions. For example, I've had to use workarounds to handle some lacking auth/permissions support, but they're currently working on improving it. Best part by far is the performance. And memory requirements is completely reasonable, depending on the size of the database.
- StavrosK 6y agoThanks, my use case isn't that demanding, so reading the docs won't be a problem. You're echoing my experience so far, thanks for your input!