Hi,
Thanks for your feedbacks. I have checked it again and found that this
behavior is rather consistent. So may be OS cache and Lucene warm up have
big impact.
Regards,
Dinh
The "usual" recommendation is just to fire up a series of warmup
queries at startup if you really require the first queries to be fast.
Best
Erick
On Tue, Nov 17, 2009 at 2:43 PM, Scott Ribe wrote:
> > Most likely due to the operating system caching the relevant portions of
> the
> > index after
> Most likely due to the operating system caching the relevant portions of the
> index after the first set of queries.
I have enough RAM to keep the Lucene indexes in memory all the time, so I
"dd ... > /dev/null" the files at boot. And also perform a single query to
force JIT of the query code. T
Hello,
Most likely due to the operating system caching the relevant portions of the
index after the first set of queries.
Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
- Original Message
> From: Din