Pretty much. The queryResultCache is pretty inexpensive. But be a bit
careful, it's tempting to increase it greatly, but that only buys you
performance if you see your users actually ask for subsequent pages
reasonably often
Best
Erick
On Tue, Jan 29, 2013 at 1:38 PM, Isaac Hebsh wrote:
>
Yep, the query results are stored on the server. All you get
back on the client side is the XML you see, there's nothing
else magically stored on the client.
Best
Erick
On Sun, Oct 7, 2012 at 12:45 PM, Jie Sun wrote:
> Hi Erik,
> no I dont have any evidence, just a precaution question.
> So acco
Hi Erik,
no I dont have any evidence, just a precaution question.
So according to your explanation, this cache only keep the document ID, so
if client paying to next group of document in the window, there will be
another query to solr server to retrieve these docs, correct?
ok that is good to kno
I wouldn't worry about it too much. The search result cache is really cheap,
each entry is simply a long value so even if you cache a lot of values it's not
much memory... It does _not_ cache the entire document.
Do you have any evidence that this will cause you problems or is this
theoretical?
any suggestions?
--
View this message in context:
http://lucene.472066.n3.nabble.com/queryResultWindowSize-vs-rows-tp401p4012336.html
Sent from the Solr - User mailing list archive at Nabble.com.
