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 Mon, 14 Mar 2016 02:40:23 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=58&rev2=59

Comment:
Clarify when load balancer might be needed.  Indicate seaprate machines for multiple replicas.

  
  A major driving factor for Solr performance is RAM.  Solr requires sufficient memory for
two separate things: One is the Java heap, the other is "free" memory for the OS disk cache.
  
- Another potential source of problems is a very high query rate.  Adding memory can sometimes
let Solr handle a higher rate.  If more query scalability is required, eventually that won't
be enough, and you will need to add multiple replicas of your index to scale further.  In
some circumstances, replicas might require a load balancer.
+ Another potential source of problems is a very high query rate.  Adding memory can sometimes
let Solr handle a higher rate.  If more query scalability is required, eventually that won't
be enough, and you will need to add multiple replicas of your index on multiple machines (preferably
separate physical hardware) to scale further.  For standalone Solr instances or when using
SolrCloud with clients that are not cloud-aware, multiple replicas might require a load balancer.
  
  It is strongly recommended that Solr runs on a 64-bit Java.  A 64-bit Java requires a 64-bit
operating system, and a 64-bit operating system requires a 64-bit CPU.  There's nothing wrong
with 32-bit software or hardware, but a 32-bit Java is limited to a 2GB heap, which can result
in artificial limitations that don't exist with a larger heap.  The Java heap is discussed
in a later section of this page.
  

Mime
View raw message