Re: First request for search is taking longer time and subequent requests are very fast

Hi I have 3 instances running for this. 1. Windows + tomcat 2. Linux + tomcat 3. Linx + WebSphere I observed this problem on all the 3 instances. Thanks Ravi Michael McCandless-2 wrote: > > > Which OS are you on? > > It's possible the OS has decided to swap Tomcat's pages out to use RAM >

Re: First request for search is taking longer time and subequent requests are very fast

Which OS are you on? It's possible the OS has decided to swap Tomcat's pages out to use RAM as IO cache for other processes, instead. Mike thiruvee wrote: Hi David, Thanks for your reply. 1. I will try having warm up queries after index is created, that will solve to some extent. 2.

Re: First request for search is taking longer time and subequent requests are very fast

Hi David, Thanks for your reply. 1. I will try having warm up queries after index is created, that will solve to some extent. 2. The biggest problem is server would be idle for long time. I am using spring in my project and the searcher,reader are singleton objects managed by spring. I don't u

Re: First request for search is taking longer time and subequent requests are very fast

Hi, Searcher and IndexReader use an internal cache, when your searcher is created the first query is slow cause lucene fills its cache. We re-use whenever possible searchers and readers instances. I've heard on this list that it's also a solution to launch warmup queries just after reader/sear