3 ms·
Interesting that they're testing full-text search on the two, it would be very interesting to benchmark it against something like ElasticSearch or another scala
by avar 15y ago
Interesting that they're testing full-text search on the two, it would be very interesting to benchmark it against something like ElasticSearch or another scalable full-text search engine to see how fast that would be by comparison.
- gav 15y agoOracle knows that their full-text search is lacking and have made some recent acquisitions around search. It will be interesting to see how these play out.
- lobster_johnson 15y agoYep. ElasticSearch is actually quite slow, as text engines go. It seems designed to scale, rather than provide single-machine performance. Even so we are seeing very slow queries on our 8-node cluster, even for relatively simple queries and small datasets. It seems very sensitive to the result set size (ie., the maximum item number set in the query). A limit of 50 might take 500ms (which is slow but acceptable in our case) whereas 1000 results might take 3-4 seconds. The indexes are all in OS cache so disk performance is not the bottleneck.
- avar 15y agoI'd be interested to know what your index looks like / how the mapping is set up / what the datasize is / what sort of queries you're making, because that's definitely not my experience with it. It's lighting fast on my workloads.