Supercharging the Elasticsearch Percolator

Posted by traxmaxx on Thursday October 15, 2015 @07:54AM
from the underthehood.meltwater.com dept.

http://underthehood.meltwater.com/blog/2015/09/29/supercharging-the-elasticsearch-percolator/

( 4 comments | 40 points | on HN )

Re:Supercharging the Elasticsearch Percolator by petard on Thursday October 15, 2015 @11:36AM (#10393751)

What are your memory settings for utilizing the 360GB RAM with ElasticSearch?

[ Parent | on HN ]

Re:Supercharging the Elasticsearch Percolator by alxnlssn on Thursday October 15, 2015 @01:16PM (#10394448)

Currently running with three ES data nodes per physical machine, with 30GB -Xmx allocated to each instance.

[ Parent | on HN ]

Re:Supercharging the Elasticsearch Percolator by rchakra3 on Thursday October 15, 2015 @01:15PM (#10394445)

Can you explain how a positional query is a subset of boolean queries?

Intuitively it feels like the reverse would be true.

[ Parent | on HN ]

Re:Supercharging the Elasticsearch Percolator by bergetp on Thursday October 15, 2015 @02:50PM (#10395147)

You're right, but the point here is that positional queries are boolean queries plus positions. For example, document that match 'a NEAR b' are a subset of documents matching 'a AND b'. So if 'a AND b' has no matches, there is no need to execute the more expensive 'a NEAR b'.

[ Parent | on HN ]