For indexing, is the master node CPU around 90%? If not, you aren’t sending requests fast enough or your disk is slow.
For querying, 200 facet fields is HUGE. That will take a lot of Java heap memory and will be slow. Each facet fields requires large in-memory arrays and sorting. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jan 18, 2020, at 9:29 AM, Rajdeep Sahoo <rajdeepsahoo2...@gmail.com> wrote: > > Hi shawn, > Thanks for this info, > Could you Please address my below query, > > > We are having 2.3 million documents and size is 2.5 gb. > With this data do we need solr cloud. > > 10 core cpu and 24 gb ram . 16 slave nodes. > > Still some of the queries are taking 50 sec at solr end. > As we are using solr 4.6 . > Other thing is we are having 200 (avg) facet fields in a query. > And 30 searchable fields. > Is there any way to identify why it is taking 50 sec for a query. > Multiple concurrent requests are there. > > And how to optimize the search response time as it is almost 1 mins for > some request. > > > On Sat, 18 Jan, 2020, 10:52 PM Shawn Heisey, <apa...@elyograg.org> wrote: > >> On 1/18/2020 9:55 AM, Rajdeep Sahoo wrote: >>> We do parallel indexing in production, >>> >>> What about search performance in solr cloud in comparison with master >>> slave. >>> And what about block join performance in solr cloud. >>> Do we need to increase the infra for solr cloud as we would be >>> maintaining multiple shard and replica. >>> Is there any co relation with master slave set up. >> >> As I said before, SolrCloud is not a magic bullet that solves >> performance issues. If the index characteristics are the same (number >> of docs, total size), performance in SolrCloud will be nearly identical >> to non-cloud. >> >> Thanks, >> Shawn >>
