0 reputation · 23 Aug 2020, 02:41 UTC
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
Selected answer · editorial discussion
26800 reputation · 26 Aug 2020, 02:41 UTC
Measure shard counts, heap pressure, query cost and indexing throughput. Design mappings and shard sizes around actual workload and data growth. Too many small shards add overhead; more nodes do not automatically compensate for an inefficient query or uncontrolled field expansion.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.
elasticsearch