are you indexing at the same time? And when you say "exact same queries", is this the same _form_ or the same query over and over? If the latter, then the responses are being served from the queryResultCache probably. Which doesn't explain why 2 and 3 take more time.
It is _vaguely_ possible that other activity on your system is swapping out OS memory that is being used for the MMapDirectory and that firing these queries _more_ often would flatten out those spikes. Frankly, though, that is very unlikely. 20 seconds to swap back in some memory is a very, _very_ long time. This is a "lunatic fringe" kind of possibility that I thought worth mentioning... Could we see the queries you fire? Best, Erick On Fri, May 30, 2014 at 12:19 PM, drmangrum <drmang...@yahoo.com> wrote: > I don't think that's the case. Ignoring the results from the admin screen, > I'm still left with inconsistencies within the SolrJ calls. > > I ran the exact same query (a simple integer equality returning 9 > documents) > 5 times every 10 seconds through solrJ and I get the following results (3 > separate executions): > > Run 1 > 1) 259ms > 2) 21030ms > 3) 21030ms > 4) 27ms > 5) 24ms > > Run 2 > 1) 42292ms > 2) 26ms > 3) 23ms > 4) 24ms > 5) 22ms > > Run 3 > 1) 252ms > 2) 21030ms > 3) 21028ms > 4) 27ms > 5) 24ms > > No indexing is occurring, so searchers and caches shouldn't be invalidated, > right? I'm inclined to believe the fast results are from the cache and the > ~250ms results from a fresh query, but what could cause the spikes of 21 > and > 42 seconds? Is it possible I'm missing a setting within the construction > of > the client-side CloudSolrServer object? > > Thanks, > Ryan > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Inconsistent-query-times-tp4138956p4138966.html > Sent from the Solr - User mailing list archive at Nabble.com. >
