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 951E4109EB for ; Thu, 5 Dec 2013 09:12:54 +0000 (UTC) Received: (qmail 68706 invoked by uid 500); 5 Dec 2013 09:12:17 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 68641 invoked by uid 500); 5 Dec 2013 09:12:14 -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 68613 invoked by uid 99); 5 Dec 2013 09:12:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 09:12:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [74.125.83.49] (HELO mail-ee0-f49.google.com) (74.125.83.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 09:12:04 +0000 Received: by mail-ee0-f49.google.com with SMTP id c41so2857011eek.22 for ; Thu, 05 Dec 2013 01:11:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=TB5GOIDp4NrpGsZAOCyif46+T+0BKksPrYkfPIUKgoc=; b=csdU4TUll94+koDVTv89BxpNz6/tXFYUdPwgvOFglMn2Q6ESWszGY49h/Sm9TMgG/x VqckkplQM73v8Rl7KAglrPbBq3ExzFiuc0xgLqX0nGp/MGs9gwnZ7v48M0ibftOFPyhx lGpYyQeuH0eRGymPa9Psu1Mfw7UFtIdmvccilkVYjIGlrTSelpMzRH6gQAKFdtZ0z26b ElFcanAHVRSi87CbAxu6J0HtBN5EEBo8JzVGEfs/91cS7NKtfCthgxL+9SLqkZUIY34k wukh1F578RPaLXB750aKViIssUF3vIWcGQsXW7t35OWpBOcRrhLJ4gSu7fnu4XrnkYJv AMNA== X-Gm-Message-State: ALoCoQkabKjNhn+XyvtsBY+FdIOGiHwYjloTrOMaJDo+yhKlHUg8ArG45s6YWIecskdKL/VoKhjZ MIME-Version: 1.0 X-Received: by 10.15.23.206 with SMTP id h54mr79699788eeu.17.1386234704255; Thu, 05 Dec 2013 01:11:44 -0800 (PST) Received: by 10.15.82.4 with HTTP; Thu, 5 Dec 2013 01:11:44 -0800 (PST) In-Reply-To: References: Date: Thu, 5 Dec 2013 14:11:44 +0500 Message-ID: Subject: Re: SOLR 4 not utilizing multi CPU cores From: Salman Akram To: Solr Group Content-Type: multipart/alternative; boundary=089e01634ab41f5fd004ecc5eb91 X-Virus-Checked: Checked by ClamAV on apache.org --089e01634ab41f5fd004ecc5eb91 Content-Type: text/plain; charset=ISO-8859-1 More info on Cpu consumption: We have a server with 32 physical cores. Same search when executed on SOLR 4.6 takes quite long and throughout only uses 3% cpu (1 core). Same search when executed on SOLR 1.4.1 takes much less time and on average uses around 40-50% cpu. On Thu, Dec 5, 2013 at 2:05 PM, Salman Akram < salman.akram@northbaysolutions.net> wrote: > I missed one imp piece of info. Due to large size we have indexed the date > with Common Grams. All of the words in slow search are in common grams and > when I debug it, they query is made properly with common grams. > > In debug all of the time is shown in process query time. > > Let me know what other info you need? Thanks > > > On Thu, Dec 5, 2013 at 11:38 AM, Andrea Gazzarini wrote: > >> Hi, I did moreless the same but didn't get that behaviour...could you give >> us more details >> >> Best, >> Gazza >> On 5 Dec 2013 06:54, "Salman Akram" >> wrote: >> >> > Hi, >> > >> > We recently upgraded to SOLR 4.6 from SOLR 1.4.1. Overall the >> performance >> > went down for large phrase queries. On some analysis we have seen that >> > 1.4.1 utilized multiple cpu cores for such queries but SOLR 4.6 is only >> > utilizing single cpu core. Any idea on what could be the reason? >> > >> > Note: We are not using SOLR Sharding. >> > >> > -- >> > Regards, >> > >> > Salman Akram >> > >> > > > > -- > Regards, > > Salman Akram > > -- Regards, Salman Akram --089e01634ab41f5fd004ecc5eb91--