ginal Message-
> From: Alan Woodward [mailto:a...@flax.co.uk]
> Sent: Montag, 8. Juni 2015 12:23
> To: java-user@lucene.apache.org
> Subject: Re: Memory problem with TermQuery
>
> Hi Anna,
>
> In normal usage, perReaderTermState will be null, and TermQuery will be very
&g
@lucene.apache.org
Subject: Re: Memory problem with TermQuery
Hi Anna,
In normal usage, perReaderTermState will be null, and TermQuery will be very
lightweight. It's in particular expert use cases (generally after queries have
been rewritten against a specific IndexReader) that the perReaderTermState wil
itten queries somehow?
Alan Woodward
www.flax.co.uk
On 8 Jun 2015, at 10:49, Anna Maier wrote:
> Hi,
>
> we ran into a memory problem with TermQuery: in our program, we build a
> TermQuery object from the user input and pass it around, to be able to
> different things, like execute
Hi,
we ran into a memory problem with TermQuery: in our program, we build a
TermQuery object from the user input and pass it around, to be able to
different things, like execute the query again and so on. So, the TermQuery
object can potentially exist for some time.
Now it turns out, that a
lkay polat wrote:
> I have also confused about the memory management of lucene.
>
> Where is this out of memory problem is mainly arised from Reason-1 or
> Reason-2 reason?
>
> Reason-1 : Problem is sourced from searching is done in big indexed file
> (nearly 40 GB) If there is
I have also confused about the memory management of lucene.
Where is this out of memory problem is mainly arised from Reason-1 or Reason-2
reason?
Reason-1 : Problem is sourced from searching is done in big indexed file
(nearly 40 GB) If there is 100(small number of records) records
ubject: Re: Out of memory problem in search
To: java-user@lucene.apache.org
Date: Wednesday, July 14, 2010, 2:59 PM
Certainly it will. Either you need to increase your memory OR refine your
query. Eventhough you display paginated result. The first couple of pages
will display fine and going toward
8GB in maximum situation)?
--- On Wed, 7/14/10, Uwe Schindler wrote:
From: Uwe Schindler
Subject: RE: Out of memory problem in search
To: java-user@lucene.apache.org
Date: Wednesday, July 14, 2010, 3:25 PM
Reverse the query sorting to display the last page.
-
Uwe Schindler
H.-H.-Meier-Allee
o: java-user@lucene.apache.org
> Subject: Out of memory problem in search
>
> Hello Friends;
>
> Recently, I have problem with lucene search - memory problem on the basis
> that indexed file is so big. (I have indexed some kinds of information and
this
> indexed file'
last100 objects are returned. The memory is consumed in creating these
objects.
Regards
Aditya
www.findbestopensource.com
On Wed, Jul 14, 2010 at 4:14 PM, ilkay polat wrote:
> Hello Friends;
>
> Recently, I have problem with lucene search - memory problem on the basis
> that indexe
Hello Friends;
Recently, I have problem with lucene search - memory problem on the basis that
indexed file is so big. (I have indexed some kinds of information and this
indexed file's size is nearly more than 40 gigabyte. )
I search the lucene indexed file
lso to put
> topdocs to null and the query and queryparse I use to get the doc to null
> aswell but nothing changes.
> Has someone experienced this problem?.
> I am using lucene 2.4 but with 2.3 was the same
> Sorry for my english and thanks in advanced.
>
> --
> View this
aswell but nothing changes.
Has someone experienced this problem?.
I am using lucene 2.4 but with 2.3 was the same
Sorry for my english and thanks in advanced.
--
View this message in context:
http://www.nabble.com/Memory-problem-dealing-with-indexsearcher-and-topdocs-tp20168138p20168138.html
Sent
tance as soon as all clients that were using it are done.
- Original Message -
From: "Chris Hostetter" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, February 01, 2006 6:03 PM
Subject: Re: Memory problem
it seems like there are a few common things that bite people over
prevent norms from being calculated, which can save a lot of space.
: Date: Wed, 1 Feb 2006 10:21:55 -
: From: Leon Chaddock <[EMAIL PROTECTED]>
: Reply-To: java-user@lucene.apache.org
: To: java-user@lucene.apache.org
: Subject: Memory problem
:
: Hi All,
:
As long as you have many document in index there can many unique terms
in index.
Every 128th term(by default) is written to term info index for faster
term lookup.
This info is loaded entirely to memory when searching so this can
increase memory usage.
Note that this does not depends on number o
Hi Nick,
we didnt get the error on importing it was actually when conducting a
search. Would this still help?
Thanks
Leon
- Original Message -
From: "Nick Vincent" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, February 01, 2006 11:17 AM
Subject: RE: Memory problem
H
Chaddock [mailto:[EMAIL PROTECTED]
Sent: Wed 01/02/2006 10:21
To: java-user@lucene.apache.org
Subject: Memory problem
Hi All,
We have a lucene index of over 10 000 000 docs at this time.
When we try and run a search we get
java.lang.OutOfMemoryError: Java heap space
We have tried setting the xmx
Hi All,
We have a lucene index of over 10 000 000 docs at this time.
When we try and run a search we get
java.lang.OutOfMemoryError: Java heap space
We have tried setting the xmx settings to 1gb but to no avail (the box has
4gb of memory available) . IS there any guidance on handling memory or
19 matches
Mail list logo
