Thanx a lot Adrien.
On Fri, Feb 17, 2017 at 10:07 PM, Adrien Grand wrote:
> Some minimal information about the fields is loaded into memory when you
> open the index reader. Things like the list of fields and how they are
> indexed.
>
> However the vast majority of the data is read from disk laz
Some minimal information about the fields is loaded into memory when you
open the index reader. Things like the list of fields and how they are
indexed.
However the vast majority of the data is read from disk lazily, we do not
warm the filesystem cache or anything like that by default. We do not u
Hey, thank you so much. I got it.
I have
- 10 lakh docs, 30 fields in my index
- opening new searcher at initial search and
- there will be no filesystem cache for my current index
At initial search, I search across only one field out of 30 fields in my
index.
My question is,
*At init
Regarding whether the filesystem cache helps, you could look at whether
there is some disk activity while your queries are running.
When everything is in the filesystem cache, the latency of search requests
for simple queries (term queries and combinations through boolean queries)
usually mostly d
there was a thread discussing the performance differneces just recently...
http://www.nabble.com/forum/Search.jtp?forum=44&local=y&query=MultiReader+MultiSearcher
: Date: Fri, 7 Jul 2006 16:34:08 +0100
: From: Mike Streeton <[EMAIL PROTECTED]>
: Reply-To: java-user@lucene.apache.org
: To: java
