Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Mime-Version: 1.0
Message-Id: <p06240807c2c089630cdc@[192.168.1.34]>
In-Reply-To: <11608209.post@talk.nabble.com>
References: <11608209.post@talk.nabble.com>
Date: Sun, 15 Jul 2007 19:34:02 -0700
To: java-user@lucene.apache.org
From: Ken Krugler <kkrugler_lists@transpac.com>
Subject: Re: Serving remote lucene client - RMI vs HTTP
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

>Hi Everyone,
>
>We are using lucene,nutch and spring framework to create a specialized
>search engine. Due to growing traffic we are trying to scale. By doing some
>tests we found out that the bottle neck was lucene search. We used some
>heavy traffic simulation and logged the time taken by each portion of the
>server response and found out that the bulk of the time was spent in
>searching from lucene index.
>
>In order to accomodate higher traffic we are planning on splitting our
>application in 2 portions:
>1. Web application (on 1 machine)
>2. Search application (one more than 1 machine)

[snip]

Nutch already supports distributed Lucene searchers, using Hadoop RPC.

-- Ken
-- 
Ken Krugler
Krugle, Inc.
+1 530-210-6378
"If you can't find it, you can't fix it"

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org