Thanks for the comments. Sounds like I will probably be ok.
-Original Message-
From: Jason Rutherglen [mailto:jason.rutherg...@gmail.com]
Sent: Friday, June 19, 2009 1:50 PM
To: java-user@lucene.apache.org; java-...@lucene.apache.org
Subject: Re: caching an indexreader
On the topic of
On the topic of RAM consumption, it seems like field caches
could return estimated RAM usage (given they're arrays of
standard Java types)? There's methods of calculating per
platform (I believe relatively accurately).
On Fri, Jun 19, 2009 at 12:11 PM, Michael McCandless <
luc...@mikemccandless.co
On Fri, Jun 19, 2009 at 2:40 PM, Scott Smith wrote:
> In my environment, one of the concerns is that new documents are
> constantly being added (and some documents may be deleted). This means
> that when a user does a search and pages through results, it is possible
> that there are new items comi
> As I understand it, the user won't see any changes to the
index until a new Searcher is created.
Correct.
> How much memory will caching the searcher cost? Are there
other tradeoff's I need to consider?
If you're updating the index frequently (every N seconds) and
the searcher/reader is closed
