Search Benchmarking: RediSearch vs. Elasticsearch
redislabs.com
Search Benchmarking: RediSearch vs. Elasticsearch
1–10 of 81 posts
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#2Someone needs to edit this article. There are misspellings and typos all over the place.
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#3The article is a mess of misspellings and misquotes. Also why two distributed search engine were tested on a single node? That's a a meaningless test.
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#4I'm curious if this scales down well. The test was done on "One AWS c4.8xlarge with 36vCPU and 60GiB Memory". But could I run this on a tiny vps to index, search, catalog my million-odd documents?
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#5I'm curious if this scales down well. The test was done on "One AWS c4.8xlarge with 36vCPU and 60GiB Memory". But could I run this on a tiny vps to index, search, catalog my million-odd documents?
I'd guess redis performs _better_ in that case since there minimum overhead for redis is much lower than elasticsearch.
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#6I've seen a lot of ES competitor posts pop up on HN lately, and I think they're missing the point of Elastic.
If you only need very basic word search, ES is probably not worth the complexity in your stack, especially if you're already running a SQL database with decent plaintext search.
Where elasticsearch shines is in complex queries: "Show me every match where this field contains 'extinction' within 10 words of 'impact crater' but NOT containing 'oceanic' and the publish date is > last month and one of the subjects is anthropology"
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#7I'm curious if this scales down well. The test was done on "One AWS c4.8xlarge with 36vCPU and 60GiB Memory". But could I run this on a tiny vps to index, search, catalog my million-odd documents?
I'd guess redis performs _better_ in that case since there minimum overhead for redis is much lower than elasticsearch.
Wouldn't Redis need to keep the whole dataset in memory?
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#8[deleted]
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#9Earlier quoted context omitted.
I'd guess redis performs _better_ in that case since there minimum overhead for redis is much lower than elasticsearch.
Wouldn't Redis need to keep the whole dataset in memory?
In my experience to get decent "show off in benchmarks" performance with ES you want your index to fit in RAM as well, but I haven't done much work with ES outside of high RAM boxes.
Re: Search Benchmarking: RediSearch vs. Elasticsearch
#10Does not tell us the settings for text analysis done by two engines. Secondly on query side - again, scoring settings of RediSearch vs Elastic are not discussed.
With that it’s just 2 points in space which gives us little information to deduce 58% faster at X or whatever.