lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "SolrPerformanceProblems" by ShawnHeisey
Date Tue, 01 Nov 2016 13:24:58 GMT
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=66&rev2=67

Comment:
Added something to the special note about optimizes, indicating that this can also be a factor
with replication.

  
  ==== Special note regarding the optimize operation ====
  
- Optimizing your index results in a large amount of disk I/O.  If you don't have enough OS
disk cache to effectively cache your index, an optimize operation can be *very* disruptive
to normal Solr operation.  If optimizes are something that will happen frequently, it may
be a requirement that you have enough RAM to cache at least 100 percent of your index contents.
 Performance during an optimize will be best if you have enough RAM to cache both the original
and the optimized versions of the index at the same time.
+ Optimizing your index results in a large amount of disk I/O.  If you don't have enough OS
disk cache to effectively cache your index, an optimize operation can be *very* disruptive
to normal Solr operation.  If optimizes are something that will happen frequently, it may
be a requirement that you have enough RAM to cache at least 100 percent of your index contents.
 Performance during an optimize will be best if you have enough RAM to cache both the original
and the optimized versions of the index at the same time.  This note can also apply to slave
servers doing replication, if a large merge or an optimize happens on the master server.
  
  === Java Heap ===
  

Mime
View raw message