Well, you could invoke it manually yourself, to warm up a just-opened reader?
But it may be better to run "typical" known queries instead, since that will tickle the index parts that your application uses... Mike McCandless http://blog.mikemccandless.com On Fri, Apr 15, 2016 at 7:38 AM, Yonghui Zhao <zhaoyong...@gmail.com> wrote: > Thanks Michael. > > Will this also help restart of service with static index? > > 2016-04-15 17:30 GMT+08:00 Michael McCandless <luc...@mikemccandless.com>: > >> There is also SimpleMergedSegmentWarmer, which you can set on >> IndexWriterConfig when you create IndexWriter so that it pre-warms >> newly merged segments before making them visible to the next >> near-real-time reader. >> >> Mike McCandless >> >> http://blog.mikemccandless.com >> >> >> On Fri, Apr 15, 2016 at 3:04 AM, Yonghui Zhao <zhaoyong...@gmail.com> >> wrote: >> > As we know when a new IndexReader is create, search performance is very >> bad. >> > So we should warm up the reader before serving real traffic. >> > >> > A simple way is to send some mocked queries. >> > >> > Is there any elegant or built-in method? >> > >> > Thanks >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-user-h...@lucene.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
