We are having 2.3 million documents and size is 2.5 gb.
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.
On Sat, 18 Jan, 2020, 10:32 PM Dave, <hastings.recurs...@gmail.com> wrote:
> Agreed with the above. what’s your idea of “huge”? I have 600 ish gb in
> one core plus another 250x2 in two more on the same standalone solr
> instance and it runs more than fine
>
> > On Jan 18, 2020, at 11:31 AM, Shawn Heisey <apa...@elyograg.org> wrote:
> >
> > On 1/18/2020 1:05 AM, Rajdeep Sahoo wrote:
> >> Our Index size is huge and in master slave the full indexing time is
> almost
> >> 24 hrs.
> >> In future the no of documents will increase.
> >> So,please some one recommend about the no of nodes and configuration
> like
> >> ram and cpu core for solr cloud.
> >
> > Indexing is not going to be any faster in SolrCloud. It would probably
> be a little bit slower. The best way to speed up indexing, whether running
> SolrCloud or not, is to make your indexing processes run in parallel, so
> that multiple batches of documents are being indexed at the same time.
> >
> > SolrCloud is not a magic bullet that solves all problems. It's just a
> different way of managing indexes that has more automation, and makes
> initial setup of a distributed index a lot easier. It doesn't do the job
> any faster than running without SolrCloud. The legacy master/slave mode is
> likely to be a little bit faster.
> >
> > You haven't provided any of the information required for us to guess
> about the system requirements. And it will be a guess ... we could be
> completely wrong.
> >
> >
> https://lucidworks.com/post/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/
> >
> > Thanks,
> > Shawn
>
