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
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
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
Thank you so much for your reply.
I know that you answered this question before. I just
wanted to post the question to receive more feedbacks
and share the information.
Thanks again.
Amany M.
--- Otis Gospodnetic <[EMAIL PROTECTED]>
wrote:
> I think I answered that question just the other
> da
I think I answered that question just the other day privately...
No, there is nothing in Lucene to help you with CPU utilization.
However, if you are running this on a UNIX box of some kind, you can (re)nice
the process and thus lower its priority, giving other processes more time with
the CP
