Hello,
I am building a Lucene index with over a million
documents retrieved from database. I am running the
application on Unix, I am getting a 100% CPU
utilization the moment the application start.
The application creates a list of small indices in a
temp directory then merge them all in the
Hi,
We have a large index that we divide into X lucene indices - we use lucene
6.5.0. On each of our serving machines serves 8 lucene indices in parallel.
We are getting realtime updates to each of these 8 indices. We are seeing a
couple of things:
a) When we turn off realtime updates, performanc
CPU. Windows may have something similar.
Otis
- Original Message
From: Amany Moussa <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Monday, February 20, 2006 9:50:57 AM
Subject: Lucene CPU Utilization
Hello,
I am building a Lucene index with over a million
doc
ows may have something similar.
>
> Otis
>
> - Original Message
> From: Amany Moussa <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Monday, February 20, 2006 9:50:57 AM
> Subject: Lucene CPU Utilization
>
>
> Hello,
>
> I a
ng
diCarta, Inc.
-Original Message-
From: Amany Moussa [mailto:[EMAIL PROTECTED]
Sent: Mon 2/20/2006 12:22 PM
To: java-user@lucene.apache.org
Cc:
Subject: Re: Lucene CPU Utilization
Thank you so much for your reply.
I know that you answered this question before. I just
I think the usual usage pattern is to *refresh* frequently and commit
less frequently. Is there a reason you need to commit often?
You may also have overlooked this newish method: MergePolicy.findFullFlushMerges
If you implement that, you can tell IndexWriter to (for example) merge
multiple small
Thanks, Michael. Its good to know that scorers are also doing matching. I
will check and verify whether the scores returned are 0 or not.
Just to give some background, we have two setups:
a) Old setup - Each machine serves a single lucene index which has roughly
30'ish segments with realtime updat
