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 9E57F1058F for ; Thu, 26 Dec 2013 11:24:42 +0000 (UTC) Received: (qmail 96430 invoked by uid 500); 26 Dec 2013 11:24:36 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 95969 invoked by uid 500); 26 Dec 2013 11:24:35 -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 95961 invoked by uid 99); 26 Dec 2013 11:24:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Dec 2013 11:24:33 +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: local policy) Received: from [89.161.223.23] (HELO v044473.home.net.pl) (89.161.223.23) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 26 Dec 2013 11:24:27 +0000 Received: from 078088007253.bialystok.vectranet.pl [78.88.7.253] (HELO [192.168.1.19]) by alud.home.pl [89.161.223.23] with SMTP (IdeaSmtpServer v0.80) id 741e9916709faff0; Thu, 26 Dec 2013 12:24:07 +0100 Date: Thu, 26 Dec 2013 12:23:56 +0100 From: =?utf-8?Q?Rafa=C5=82_Ku=C4=87?= Organization: Solr.pl X-Priority: 3 (Normal) Message-ID: <38526336.20131226122356@alud.com.pl> To: solr-user@lucene.apache.org Subject: Re: Solr Query Slowliness In-Reply-To: References: <1761523616.20131226114927@alud.com.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hello! Different queries can have different execution time, that's why I asked about the details. When running the scripts, is Solr CPU fully utilized? To tell more I would like to see what queries are run against Solr from scripts. Do you have any information on network throughput between the server you are running scripts on and the Solr cluster? You wrote that the scripts are fine for 5 seconds and than they get slow. If your Solr cluster is not fully utilized I would take a look at the queries and what they return (ie. using faceting with facet.limit=3D-1) and seeing if the network is able to process those.=20 --=20 Regards, Rafa=C5=82 Ku=C4=87 Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ > Thanks Rafal for your reply, > My scripts are running on other independent machines so they does not > affect Solr, I did mention that the queries are not the same (that is why= I > removed the query cache from solrconfig.xml), and I only get 1 result from > Solr (which is the top scored one so no sorting since it is by default > ordred by score) > 2013/12/26 Rafa=C5=82 Ku=C4=87 >> Hello! >> >> Could you tell us more about your scripts? What they do? If the >> queries are the same? How many results you fetch with your scripts and >> so on. >> >> -- >> Regards, >> Rafa=C5=82 Ku=C4=87 >> Performance Monitoring * Log Analytics * Search Analytics >> Solr & Elasticsearch Support * http://sematext.com/ >> >> >> > Hi all, >> >> > I have multiple python scripts querying solr with the sunburnt module. >> >> > Solr was hosted on an Amazon ec2 m1.large (2 vCPU with 4 ECU, 7.5 GB >> memory >> > & 840 GB storage) and contained several cores for different usage. >> >> > When I manually executed a query through Solr Admin (a query containing >> > 10~15 terms, with some of them having boosts over one field and limited >> to >> > one result without any sorting or faceting etc ....) it takes around 7= 00 >> > ms, and the Core contained 7 million documents. >> >> > When the scripts are executed things get slower, my query takes 7~10s. >> >> > Then what I did is to turn to SolrCloud expecting huge performance >> increase. >> >> > I installed it on a cluster of 5 Amazon ec2 c3.2xlarge instances (8 vC= PU >> > with 28 ECU, 15 GB memory & 160 SSD storage), then I created one >> collection >> > to contain the core I was querying, I sharded it to 25 shards (each no= de >> > containing 5 shards without replication), each shards took 54 MB of >> storage. >> >> > Tested my query on the new SolrCloud, it takes 70 ms ! huge increase w= ich >> > is very good ! >> >> > Tested my scripts again (I have 30 scripts running at the same time), = and >> > as a surprise, things run fast for 5 seconds then it turns realy slow >> again >> > (query time ). >> >> > I updated the solrconfig.xml to remove the query caches (I don't need >> them >> > since queries are very different and only 1 time queries) and changes = the >> > index memory to 1 GB, but only got a small increase (3~4s for each que= ry >> ?!) >> >> > Any ideas ? >> >> > PS: My index size will not stay with 7m documents, it will grow to +10= 0m >> > and that may get things worse >> >>