What version are you on. There was a bug where if you use cache size 0, it would still create a cache with size 2 (or may be just 1). It was fixed under https://issues.apache.org/jira/browse/SOLR-9886?filter=-2
On Apr 3, 2017 9:26 AM, "Nilesh Kamani" <nilesh.kam...@gmail.com> wrote: > @Yonik even though the code change is in SolrIndexer class, it has nothing > do with index itself. > After fetching docIds, I am filtering them on one more criteria. (Very > weird code it is). > > I tried q={!cache=false}, but not working. Subsequent search is done under > 2 milliseconds. > > Does anybdody have more insight on this ? > > On Fri, Mar 31, 2017 at 2:17 PM, Yonik Seeley <ysee...@gmail.com> wrote: > > > On Fri, Mar 31, 2017 at 1:53 PM, Nilesh Kamani <nilesh.kam...@gmail.com> > > wrote: > > > @Alexandre - Could you please point me to reference doc to remove > default > > > cache settings ? > > > > > > @Yonik - The code change is in Solr Indexer to sort the results. > > > > OK, so to test indexing performance, there are no caches to worry > > about (as long as you have autowarmCount=0 on all caches, as is the > > case with the Solr example configs). > > > > To test sorted query performance (I assume you're sorting the index to > > accelerate certain sorted queries), if you can't make the queries > > unique, then add > > {!cache=false} to the query > > example: q={!cache=false}*:* > > You could also add a random term on a non-existent field to change the > > query and prevent unwanted caching... > > example: q=*:* does_not_exist_s:149475394 > > > > -Yonik > > >