Hi, Only you can tell what are acceptable query latency (I can tell you ideal - it is 0 :) Usually you start test with a single shard and start adding documents to it and measure query latency. When you start being close to max allowed latency, you have your shard size. Then you try to estimate number of documents in index now/future and you divide that number by shard size to get the number of shards. You then test to see what is the number of shards you can have per node. You multiple number of shards by number of replicas you plan to have and divide by number of shards per node to estimate number of nodes. If you are not happy with numbers, you change some assumption, e.g. node type, and redo tests.
HTH, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > On 11 Apr 2018, at 15:30, neotorand <neotor...@gmail.com> wrote: > > Hi Emir, > Thanks a lot for your reply. > so when i design a solr eco system i should start with some rough guess on > shards and increase the number of shards to make performance better.what is > the accepted/ideal Response Time.There should be a trade off between > Response time and the number of shards as data keeps growing. > > I agree we split our index when response time increases.So what could be > that response time threshold or query Latency? > > Thanks again! > > > Regards > priyadarshi > > > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html