Thanks for good hints
Borek
> -Original Message-
> From: Itamar Syn-Hershko [mailto:[email protected]]
> Sent: Sunday, July 25, 2010 1:03 AM
> To: [email protected]
> Subject: Re: [CLucene-dev] Performance questions
>
> Borek,
>
> That
On 26/7/2010 10:32 AM, Ben vanklinken wrote:
> Itamar, why do you suggest one searcher per thread? The searcher is
> multithreaded.
>
Being multithreaded means having locks on certain operations. If you
have too many users depend on one searcher, performance will drop.
This is why I suggested
Itamar, why do you suggest one searcher per thread? The searcher is
multithreaded.
Borek,
I suggest you look at the architecture for nutch. They have some good
ideas implemented there.
Ben
Sent from my iPhone
On 25/07/2010, at 1:02, Itamar Syn-Hershko wrote:
> Borek,
>
> That is a good q
Borek,
That is a good question. My gut tells me it all depends on your scenario
and configurations, and you'd do best to just benchmark and see.
Reusing an IndexSearcher is definitely necessary, but if you'll be using
one searcher for multiple users then you'll have to implement some sort
of l
Hi,
I'm looking for some hints on server type application architecture from optimal
CLucene search usage point of view.
Questions like:
Share IndexSearcher objects between users or dedicate one for each user
What is the optimal number of IndexSearcher objects
One large index or smaller indexes
