At a presentation given the the author of elasticsearch's completion search feature he suggested prefering a single shard when possible. We should evaluate performance of using single shard indices (with multiple replicas as necessary) vs our current usage of 4 shards on the largest completion indices.
Description
Description
Event Timeline
Comment Actions
Semi related, at the same talk the author suggested we should be able to handle a much larger query load and referenced http://aaron.blog.archive.org/2013/05/29/worlds-biggest-fst/ as proof.
Other info from a slide about what the developer (us) should be responsible for:
Be Responsive!
- Accomodate unique request pattern
- minimize network latency
- prefer single shard index
- simplify query analysis
Be Relevant!
- Invest in suggestion weights
- Minimize number of suggestions served
- Update suggestions to reflect the latest and greatest
- cleanse suggestions
Be Forgiving!
- Chose suitable index and query time analysis
- Use typo-tolerant suggester appropriately
Comment Actions
We are currently happy with the number of shards and we optimize them for operability.