Mailing-List: contact lucy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: lucy-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gorankent@gmail.com
 designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20111109184153.GA8863@rectangular.com>
References: 
 <CAKn6EF9RB96LUw2yMux_k+68BRVWLk_tYtZnpCLJN19QpCLeNA@mail.gmail.com>
	<20111109184153.GA8863@rectangular.com>
Date: Wed, 9 Nov 2011 21:24:28 +0200
Message-ID: 
 <CAKn6EF9gy7Pw8QBJa=ZDqkfdX3f0YRfpXdafGib8xdLbmQkUPg@mail.gmail.com>
From: goran kent <gorankent@gmail.com>
To: lucy-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [lucy-user] LucyX::Remote::SearchServer concurrency

On Wed, Nov 9, 2011 at 8:41 PM, Marvin Humphrey <marvin@rectangular.com> wr=
ote:
>> Correct me if I'm miss-reading
>> the code, but doesn't that mean that serve() will block until it
>> finishes the current search =A0-- =A0ie, no concurrent searches?
>
> Yes.
>
> FWIW, Searchers are cheap, because we rely heavily on the OS cache rather=
 than
> dump stuff into process RAM. =A0That aids with multi-process concurrency,
> because adding another worker is inexpensive.

ok, what's the recommended route to facilitate concurrent searches on
a remote search server?  Rewrite LucyX/Remote/SearchServer.pm to fork
off a worker process for each new connection?

Right now off the top of my head I can't think of a way to wrap
LucyX/Remote/SearchServer.pm to achieve this.