I'm having a performance issue with my cluster (0.90.3). At ~3M docs per
shard and 5 shards per server the servers can't handle a lot of QPS (load
tests peg a single server @ ~ 80qps) - even though the entire index sits in
memory [the docs are really small]. The nodes are burning a lot of CPU and
it's not due to GC [1 CMS every 2 hours].
Here's an example query:
There's not a lot of docs about the performance of most queries on ES. I
made a few guesses and wanted to know if I was right.
- Prefer using _boost in lieu of custom_score. [I'm assuming ES can do more index-time optimizations this way].
- Merge filters at index time if possible.
- Use mapping-level boosting per-field instead of custom_boost_factor.
- [In combination with 3] Index dis_max sub-queries to _all and get rid of
Of course these will sacrifice flexibility, but at this point I'm looking
for performance wins. Do any of these ideas have basis, or is there
something else I can do to get the per server performance up?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.