You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2014/12/23 18:03:07 UTC
[Solr Wiki] Update of "SolrPerformanceProblems" by ShawnHeisey
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The "SolrPerformanceProblems" page has been changed by ShawnHeisey:
https://wiki.apache.org/solr/SolrPerformanceProblems?action=diff&rev1=36&rev2=37
Comment:
for switching to SolrCloud, mention possible need to reindex.
Here is an incomplete list, in no particular order, of how to reduce heap requirements, based on the [[SolrPerformanceProblems#Java_Heap|list above]] for things that require a lot of heap:
* Take a large index and make it distributed - shard your index onto multiple servers.
- * One very easy way to do this is to switch to SolrCloud.
+ * One very easy way to do this is to switch to SolrCloud. You may need to [[HowToReindex|reindex]] but SolrCloud will handle all the sharding for you.
* This doesn't actually reduce the overall memory requirement for a large index (it may actually increase it slightly), but spreads it across multiple servers, so each server will have lower memory requirements.
* Don't store all your fields, especially the really big ones.
* Instead, have your application retrieve detail data from the original data source, not Solr.