Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Huge performance drop in distributed search w/ shards on the same
 server/container
From: Grant Ingersoll <gsingers@apache.org>
In-Reply-To: <58B6CA2F3B4F49D2A657CC204D24C2E0@gmail.com>
Date: Fri, 13 May 2011 06:57:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5161313A-16D5-4C44-9C0E-9FDC2DF7852C@apache.org>
References: <58B6CA2F3B4F49D2A657CC204D24C2E0@gmail.com>
To: solr-user@lucene.apache.org

Is that 10 different Tomcat instances or are you using multicore?  How =
are you testing?

On May 13, 2011, at 6:08 AM, Frederik Kraus wrote:

> Hi,=20
>=20
> I'm having some serious problems scaling the following setup:
>=20
> 48 CPU / Tomcat / ...
>=20
> localhost/shard1
> ...
> localhost/shard10
>=20
> When using all 10 shards in the query the req/s drop down to about 300 =
without fully utilizing cpu (60% idle) or ram (disk i/o is zero - =
everything fits into the ram)
>=20
> When only quering one shard I get about 5k-6k req/s=20
>=20
> Are there any known limits and/or work-arounds?
>=20
> Thanks,
>=20
> Fred.

--------------------------------------------
Grant Ingersoll
Join the LUCENE REVOLUTION
Lucene & Solr User Conference
May 25-26, San Francisco
www.lucenerevolution.org