On Thu, Feb 15, 2024 at 12:38 AM Arun Sudhir wrote:
> Thanks everyone for the tips!
> @Mikhail
> I tried your suggestion and it seems to work. We do not run into the cold
> boot long query time for the particular facet query anymore. Had a
> follow-up question: Will adding three or four-facet que
Thanks everyone for the tips!
@Mikhail
I tried your suggestion and it seems to work. We do not run into the cold
boot long query time for the particular facet query anymore. Had a
follow-up question: Will adding three or four-facet queries have
performance implications for the searcher? I checked t
@Rahul Surendran facet indeed is where the time
is spent:
"process": {
"time": 1560,
"query": {
"time": 10
},
"facet": {
"time": 1545
},
On Tue, Feb 13, 2024, 6:03 AM Rahul Goswami wrote:
> Can you pass debug=true with y
Can you pass debug=true with your query to find out which phase (query or
faceting) takes more time? This is to eliminate chasing the wrong symptom
to optimize for.
-Rahul
On Tue, Feb 13, 2024 at 3:48 AM Mikhail Khludnev wrote:
> Hello, Arun.
> Why don't you warm a new searcher with a query li
Hello, Arun.
Why don't you warm a new searcher with a query listener?
On Tue, Feb 13, 2024 at 3:18 AM Arun Sudhir wrote:
> Hello,
> We use solr for our search needs and we have documents indexed on a core in
> multiple machines. Over time, the index on some machines has grown from 30
> GB to 60
On Tue, Feb 13, 2024 at 5:48 AM Arun Sudhir wrote:
> Hello,
> We use solr for our search needs and we have documents indexed on a core in
> multiple machines. Over time, the index on some machines has grown from 30
> GB to 60 GB now to a giant 133 GB. While others are still hovering around
> 80GB
Hello,
We use solr for our search needs and we have documents indexed on a core in
multiple machines. Over time, the index on some machines has grown from 30
GB to 60 GB now to a giant 133 GB. While others are still hovering around
80GB, and some others are still under 30GB. We manually control whi
