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 2013/11/01 17:17:18 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=19&rev2=20

Comment:
adding info saying that if not all fields are stored, atomic updates can't be used.

    * This doesn't actually reduce the overall heap requirement for a large index, but spreads it across multiple servers.
   * 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.
   * Use {{{facet.method=enum}}} for your facets.
   * Reduce the number of different sort parameters.
   * Reduce the size of your Solr caches.