[prev in list] [next in list] [prev in thread] [next in thread] 

List:       solr-user
Subject:    Re: multiple solr instances using same index files?
From:       "James liu" <liuping.james () gmail ! com>
Date:       2007-04-28 2:21:30
Message-ID: 5d5204510704271921g20d44009g304089969d6ba251 () mail ! gmail ! com
[Download RAW message or body]


I think performance u should notice.

when one instance do index,commit,optimize,,,it will cose much CPU,RAM.
i think it will disturb your search(when they use other solr instance)
unless u know the time they will search or search's frequency is low.


2007/4/28, Ryan McKinley <ryantxu@gmail.com>:
>
> Chris Hostetter wrote:
> > : > Essentially, I have two distinct needs - in some cases i need a
> commit
> > : > immediately after indexing one document, but most of the time it is
> fine
> > : > to wait 10 mins for changes if that has better performance.
> > :
> > : Sounds like a configuration issue... set autocommit to 10 minutes, but
> > : explicitly
> > : commit the important documents?
> > :
> > : I don't quite get why one would want two solr instances for this.
> >
> > i think he means that he has some search clinets that want to see
> changes
> > immediately, but other search clients can have more lag and he wants
> > the speed benefits of good caching for those clients
> >
>
> Yes - I want the 1% use to not disrupt the 99% (readonly) use, but the
> overall load does not require multiple machines.
>
> I want one set of users to have a large infrequently disrupted cache and
> another that has no auto warming and opens new searchers frequently.
>
> If lucene supports that, i'll give it a try!
>
> ryan
>
>


-- 
regards
jl


[prev in list] [next in list] [prev in thread] [next in thread]