Hi,
Are there performance issues during the index switch?
As the size of index gets bigger, response time slows down? Are there any
studies on this?
Thanks,
Tri
During commit?
A commit (and especially an optimize) can be expensive in terms of both
CPU and RAM as your index grows larger, leaving less CPU for querying,
and possibly less RAM which can cause Java GC slowdowns in some cases.
A common suggestion is to use Solr replication to seperate out
Hi,
Are there performance issues during the index switch?
What do you mean by index switch?
As the size of index gets bigger, response time slows down? Are there any
studies on this?
I haven't seen any studies as of yet but response time will slow down for some
components. Sorting
/11, Jonathan Rochkind rochk...@jhu.edu wrote:
From: Jonathan Rochkind rochk...@jhu.edu
Subject: Re: performance during index switch
To: solr-user@lucene.apache.org solr-user@lucene.apache.org
Date: Wednesday, January 19, 2011, 11:30 AM
During commit?
A commit (and especially an optimize) can
/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
From: Tri Nguyen tringuye...@yahoo.com
To: solr-user@lucene.apache.org
Sent: Wed, January 19, 2011 2:56:58 PM
Subject: Re: performance during index switch
Yes, during a commit
On 1/19/2011 2:56 PM, Tri Nguyen wrote:
Yes, during a commit.
I'm planning to do as you suggested, having a master do the indexing and replicating the index to a slave which leads to my next questions.
During the slave replicates the index files from the master, how does it impact
