This is a variant of "the sizing question", here's the long explanation of why there's no hard rule as Aman says:
https://lucidworks.com/2012/07/23/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/ One variant of your question is "when do you have to shard a collection". SolrCloud is not _required_ to shard a collection, it just makes it _much_ easier to manage (I'd go farther and say the circumstances must be extraordinary to shard and _not_ use SolrCloud). Assuming you do not need to shard (measured by getting adequate response time for a "reasonable" query rate) but you need to serve more queries per second, you have two choices: - older style master/slave replication so two or more copies of your index are serving queries - use SolrCloud with a single shard collection. This latter has some advantages in terms of administration, HA/DR etc. at the expense of added complexity for managing your ZooKeeper ensemble. Best, Erick On Sat, Jul 29, 2017 at 8:24 AM, Aman Tandon <amantandon...@gmail.com> wrote: > Hello Sara, > > There is hard n fast rule, performance depends on caches, RAM, hdd etc.and > how much resourced you could invest to keep the acceptable performance. > Information on Number of Indexed documents, number of dynamic fields can be > viewed from the below link. I hope this helps. > > http://lucene.472066.n3.nabble.com/Solr-limitations-td4076250.html > > On Sat, Jul 29, 2017, 13:23 sara hajili <hajili.s...@gmail.com> wrote: > >> hi all, >> I want to know when standalone solr can't be sufficient for storing data >> and we need to migrate to solr cloud?for example standalone solr take too >> much time to return query result or to store document or etc. >> >> in other word ,what is best capacity and data index size in standalone >> solr that doesn't bad effect on query running and data inserting >> performance?and after passing this index size i must switch to solr cloud? >>
