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/07/17 15:24:31 UTC

[Solr Wiki] Trivial 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=33&rev2=34

Comment:
tiny change regarding overall memory requirements with a distributed index.

  
   * 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.
-   * This doesn't actually reduce the overall heap requirement for a large index, but spreads it across multiple servers.
+   * 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.
    * Note that doing this will mean that you cannot use [[Atomic_Updates|Atomic Updates]].