On Fri, 2014-06-27 at 12:33 +0200, Sandeep Khanzode wrote:
> I have an index that runs into 200-300GB. It is not frequently updated.
"not frequently" means different things for different people. Could you
give an approximate time span? If it is updated monthly, you might
consider a full optimizati
Some points based on my experience.
You can think of SolrCloud implementation, if you want to distribute your
index over multiple servers.
Use MMapDirectory locally for each Solr instance in cluster.
Hit warm-up query on sever start-up. So most of the documents will be
cached, you will start sav
Hi,
I have an index that runs into 200-300GB. It is not frequently updated.
What are the best strategies to query on this index?
1.] Should I, at index time, split the content, like a hash based partition,
into multiple separate smaller indexes and aggregate the results
programmatically?
2.] Sh