2008/5/29 Alex <[EMAIL PROTECTED]>:
> I believe we have around 346 million documents
So that would be 346MB per indexed field that you search.
Also, if you sort on anything other than score, that will take up a
lot of memory to un-invert the field.
-Yonik
---
I believe we have around 346 million documents
Alex
> Date: Thu, 29 May 2008 18:39:31 -0400
> From: [EMAIL PROTECTED]
> To: java-user@lucene.apache.org
> Subject: Re: lucene memory consumption
>
> Alex wrote:
>> Currently
On Friday 30 May 2008 08:17:52 Alex wrote:
> Hi,
> other than the in memory terms (.tii), and the few kilobytes of opened file
> buffer, where are some other sources of significant memory consumption when
> searching on a large index ? (> 100GB). The queries are just normal term
> queries.
Norms
Alex wrote:
> Currently, searching on our index consumes around 2.5GB of ram.
> This is just a single term query, nothing that requires the in memory cache
> like in
> the FieldScoreQuery.
>
>
> Alex
>
>
>
That seems rather high. You have 10/15 million
To: java-user@lucene.apache.org
> Subject: Re: lucene memory consumption
>
> Not that I can think about. But, if you have any cached field data,
> norms array, that could be huge.
>
> Would be interested in knowing from others regarding this topic as well.
>
> Jian
>
Not that I can think about. But, if you have any cached field data,
norms array, that could be huge.
Would be interested in knowing from others regarding this topic as well.
Jian
On 5/29/08, Alex <[EMAIL PROTECTED]> wrote:
>
> Hi,
> other than the in memory terms (.tii), and the few kilobytes of
