Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B060A10202 for ; Sun, 18 Jan 2015 01:16:39 +0000 (UTC) Received: (qmail 90859 invoked by uid 500); 18 Jan 2015 01:16:37 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 90664 invoked by uid 500); 18 Jan 2015 01:16:37 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 89896 invoked by uid 99); 18 Jan 2015 01:16:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Jan 2015 01:16:36 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andrew.butkus@c6-intelligence.com designates 46.236.14.172 as permitted sender) Received: from [46.236.14.172] (HELO mail.c6-intelligence.com) (46.236.14.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Jan 2015 01:15:57 +0000 Received: from C6SERVER39.andover.c6-intelligence.com ([fe80::7c8b:6429:78b1:651a]) by c6server39.andover.c6-intelligence.com ([fe80::7c8b:6429:78b1:651a%11]) with mapi id 14.03.0123.003; Sun, 18 Jan 2015 01:15:34 +0000 From: Andrew Butkus To: "" Subject: Re: Need Debug Direction on Performance Problem Thread-Topic: Need Debug Direction on Performance Problem Thread-Index: AQHQMg1iJK7aCzKUV06Rtkln/0rAipzFFGo2 Date: Sun, 18 Jan 2015 01:15:34 +0000 Message-ID: <73A5261B-B690-4B95-A6CD-7DAF5F5A6AB4@c6-intelligence.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org &shard.info=3Dtrue Sent from my iPhone > On 17 Jan 2015, at 04:23, Naresh Yadav wrote: >=20 > Hi all, >=20 > We have single solr index with 3 fixed fields(on of field is tokenized wi= th > space) and rest dynamic fields(string fields in range of 10-20). >=20 > Current size of index is 2 GB with around 12 lakh docs and solr > nodes are of 4 core, 16 gb ram linux machines. >=20 > Writes performance is good then we tested one read query(In select query = we > are applying filter criteria on tokenized field & reading only score fiel= d, > no grouping/faceting) in two setups : >=20 > *Setup1 : *Single Node Cloud with shards=3D1, replication=3D1 > In this setup whole 12 lakh docs are on same machine. Our filter query > reading > around 10 lakh docs with only score field is taking *1 minutes*. >=20 > *Setup2 : *Two Node Cloud with shards=3D2, replication=3D1 > In this setup whole 6 lakh docs on node1 and 6 lakh on node2. Our same > filter query reading around 10 lakh docs with only score field is taking = *114 > minutes.* >=20 > Please guide us what can be possible reasons of degradation of > performance after sharding of index. How can we check where solr server > is taking time to return results. >=20 > Thanks > Naresh