Please suggest anyone On Sun, 19 Jan, 2020, 9:43 AM Rajdeep Sahoo, <rajdeepsahoo2...@gmail.com> wrote:
> Apart from reducing no of facets in the query, is there any other query > params or gc params or heap space or anything else that we need to tweak > for improving search response time. > > On Sun, 19 Jan, 2020, 3:15 AM Erick Erickson, <erickerick...@gmail.com> > wrote: > >> Add &debug=timing to the query and it’ll show you the time each component >> takes. >> >> > On Jan 18, 2020, at 1:50 PM, Rajdeep Sahoo <rajdeepsahoo2...@gmail.com> >> wrote: >> > >> > Thanks for the suggestion, >> > >> > Is there any way to get the info which operation or which query params >> are >> > increasing the response time. >> > >> > >> > On Sat, 18 Jan, 2020, 11:59 PM Dave, <hastings.recurs...@gmail.com> >> wrote: >> > >> >> If you’re not getting values, don’t ask for the facet. Facets are >> >> expensive as hell, maybe you should think more about your query’s than >> your >> >> infrastructure, solr cloud won’t help you at all especially if your >> asking >> >> for things you don’t need >> >> >> >>> On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo < >> rajdeepsahoo2...@gmail.com> >> >> wrote: >> >>> >> >>> We have assigned 16 gb out of 24gb for heap . >> >>> No other process is running on that node. >> >>> >> >>> 200 facets fields are there in the query but we will not be getting >> the >> >>> values for each facets for every search. >> >>> There can be max of 50-60 facets for which we will be getting values. >> >>> >> >>> We are using caching,is it not going to help. >> >>> >> >>> >> >>> >> >>>> On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey, <apa...@elyograg.org> >> >> wrote: >> >>>> >> >>>>> On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote: >> >>>>> 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. >> >>>> >> >>>> Searching 30 fields and computing 200 facets is never going to be >> super >> >>>> fast. Switching to cloud will not help, and might make it slower. >> >>>> >> >>>> Your index is pretty small to a lot of us. There are people running >> >>>> indexes with billions of documents that take terabytes of disk space. >> >>>> >> >>>> As Walter mentioned, computing 200 facets is going to require a fair >> >>>> amount of heap memory. One *possible* problem here is that the Solr >> >>>> heap size is too small, so a lot of GC is required. How much of the >> >>>> 24GB have you assigned to the heap? Is there any software other than >> >>>> Solr running on these nodes? >> >>>> >> >>>> Thanks, >> >>>> Shawn >> >>>> >> >> >> >>
