I can provide access to debugging on a dual xeon w/ht enabled with
100million document index.
On Thu, 15 Jul 2004 14:09:23 -0400, Aviran <[EMAIL PROTECTED]> wrote:
> This is just a subset of the entire index.
> In the project that I'm working on we have ~1500 documents (this is a
> dynamic number
Aviran wrote:
> My test index is pretty small size, about 250 documents and about 24
> fields in each document. The test is done by starting 10 threads that
> repeat simple one word query (each thread query on a different word).
> Neither range nor wildcard query is done.
> I let the test run f
Aviran wrote:
My test index is pretty small size, about 250 documents and about 24 fields
in each document.
The test is done by starting 10 threads that repeat simple one word query
(each thread query on a different word). Neither range nor wildcard query is
done.
I let the test run for about a mi
> The second one is on
> org.apache.lucene.index.SegmentReader.norms(SegmentReader.java:318)
> which is a synchronized method thus causing locks. I guess the
> synchronization is done for a good reason, but you probably know the
> answer better then me.
I'm surprised this is showing up. Can y
Aviran wrote:
The next bottleneck is not very clear. There are two candidates which appear
frequently in the thread dump.
The first one which appears more frequent then the others is using
java.lang.StrictMath.log which is used in
org.apache.lucene.search.DefaultSimilarity.idf. Definitely spending
leanQuery.java
:165)
at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:154)
Aviran
-Original Message-
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 13, 2004 10:08 AM
To: Lucene Developers List
Subject: Re: FW: Lucene Search has poor cpu utilization
Thanks, I applied your change to the code in CVS.
Maybe you can test things out with your change, and see what the next
bottleneck is.
Thanks,
Otis
--- Aviran <[EMAIL PROTECTED]> wrote:
>
> Hi all,
> First let me explain what I found out. I'm running Lucene on a 4 CPU
> server.
> While doing som
