Hi Rajdeep,
1. I assume you had enabled docValues for the facet fields, right?
2. What does your GC logs tell? Do you get freezes and CPU spikes during
intervals?
3. Caching will help in querying. I'll need to see a sample query of
yours to recommend what you can tweak.
On Tue, 2
Hi Rajdeep,
Unfortunately it's near impossible for anyone here to tell you what
parameters to tweak. People might take guesses based on their
individual past experience, but ultimately those are just guesses.
There are just too many variables affecting Solr performance for
anyone to have a good
Please suggest anyone
On Sun, 19 Jan, 2020, 9:43 AM Rajdeep Sahoo,
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 E
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,
wrote:
> Add &debug=timing to the query and it’ll show you the time e
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 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 J
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, wrote:
> If you’re not getting values, don’t ask for the facet. Facets are
> expensive as hell, maybe you should think more
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 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
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 q
Although we are having a avg of 200 facet fields in the search request all
of them will not be having values in each request.
Max of 50-60 facet fields will be having some value.
And we are using function query,is it having some performance impact.
On Sat, 18 Jan, 2020, 11:10 PM Walter Unde
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
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
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
maintainin
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 wa
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 wrote:
>
> On 1/18/2020 1:05 AM, Rajdeep Sahoo wrote:
>> Our Index size
Hi shawn,
Thanks for your reply
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 sha
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
Got your point.
If we think about the infra, then in cloud do we need more infra in
comparison to master slave.
On Sat, 18 Jan, 2020, 2:24 PM Jörn Franke, wrote:
> I think you should do your own measurements. This is very document and
> processing specific.
> You can run a test with a simple
I think you should do your own measurements. This is very document and
processing specific.
You can run a test with a simple setup for let’s say 1 mio document and
interpolate from this. It could be also that your ETL is the bottleneck and not
Solr.
At the same time you can simulate user queries
How big? We index 35 million documents in about 6 hours.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 18, 2020, at 12:05 AM, Rajdeep Sahoo
> wrote:
>
> Our Index size is huge and in master slave the full indexing time is almost
> 24 hrs.
>
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.
On Sat, 18 Jan, 2020, 8:05 AM Walter Underwood,
wrote:
>
Why do you want to change to Solr Cloud? Master/slave is a great, stable
cluster architecture.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 17, 2020, at 6:19 PM, Rajdeep Sahoo wrote:
>
> Please reply anyone
>
> On Sat, 18 Jan, 2020, 12:13 A
Please reply anyone
On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo,
wrote:
> Hi all,
> We are using solr cloud 7.7.1
> In a live production environment how many solr cloud server do we need,
> Currently ,we are using master slave set up with 16 slave server with
> solr 4.6.
> In solr cloud do we
23 matches
Mail list logo
