You are right.
Cheers,
Zhibin
From: Chris Lu <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Monday, November 17, 2008 11:13:44 PM
Subject: Re: how to estimate how much memory is required to support the large
index search
So looks like you a
Thanks,
Zhibin
From: Chris Lu <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Monday, November 17, 2008 7:07:21 PM
Subject: Re: how to estimate how much memory is required to support
the
large index search
Calculation looks right. But wha
ay, November 17, 2008 7:07:21 PM
> Subject: Re: how to estimate how much memory is required to support the
> large index search
>
> Calculation looks right. But what's the "Index divisor" that you mentioned?
>
> --
> Chris Lu
> -
> Ins
gt; search is good even using index divisor as 4.
>
> Thanks,
>
> Zhibin
>
>
>
>
>
> From: Aleksander M. Stensby <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Monday, November 17, 2008 2:31:04 AM
> Subject: Re: how to
hibin
>
>
>
>
>
> From: Aleksander M. Stensby <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Monday, November 17, 2008 2:31:04 AM
> Subject: Re: how to estimate how much memory is required to support the
> large index
From: Aleksander M. Stensby <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Monday, November 17, 2008 2:31:04 AM
Subject: Re: how to estimate how much memory is required to support the large
index search
One major factor that may result in heap space problems is if you are
One major factor that may result in heap space problems is if you are
doing any form of sorting when searching. Do you have any form of default
sort in your application? Also, the type of field used for sorting is
important with regard to memory consumption.
This issue has been discussed be
Hello,
I
am a beginner on using lucene. We developed an application to
create and search index using lucene 2.3.1. We would like to know how
to estimate how much memory is required to support
the index search given an index.
Recently,
the size of the index has reached to about 200GB with 197M of