Just wanted to add the solution to this problem, in case someone finds
the matching description in the archives (see below).
By reducing the granularity of the timestamp field (stored as slong)
from seconds to minutes the number of unique values was reduced by an
order of magnitude (there are abou
Hi again,
in the meantime I discovered the use of jmap (I'm not a Java programmer)
and found that all the memory was being used up by String and char[]
objects.
The Lucene docs have the following to say on sorting memory use:
> For String fields, the cache is larger: in addition to the above
arr
Hi Otis,
thanks for the hint. Turns out I have 17.8 million unique terms. I'm
fairly sure by now that the problem lies with the sorting. In the Lucene
java docs
(http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/javadoc/org/apache/lucene/search/Sort.html)
it is stated that
> Sorting u
ene - Solr - Nutch
- Original Message
From: Otis Gospodnetic <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Thursday, November 22, 2007 10:15:23 PM
Subject: Re: Memory use with sorting problem
I'd have to check, but Luke handler might spit that out. If not,
Lucene&#
e.org
Sent: Thursday, November 22, 2007 7:22:56 AM
Subject: Re: Memory use with sorting problem
Thanks for your reply. I made some memory saving changes, as per your
advice, but the problem remains.
> Set the max warming searchers to 1 to ensure that you never have more
> than one warming at th
Thanks for your reply. I made some memory saving changes, as per your
advice, but the problem remains.
> Set the max warming searchers to 1 to ensure that you never have more
> than one warming at the same time.
Done.
> How many documents are in your index?
Currently about 8 million.
> If you
On Nov 21, 2007 11:06 AM, Chris Laux <[EMAIL PROTECTED]> wrote:
> Now when I reduce the size of caches (to a fraction of the default
> settings) and number of warming Searchers (to 2),
Set the max warming searchers to 1 to ensure that you never have more
than one warming at the same time.
> memo
Hi all,
I've been struggling with this problem for over a month now, and
although memory issues have been discussed often, I don't seem to be
able to find a fitting solution.
The index is merely 1.5 GB large, but memory use quickly fills out the
heap max of 1 GB on a 2 GB machine. This then works
