Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: <CAPXaUT48kvtQ1r=yMDZCg_6mCVQCCQXrsmzWKMkh97JotARTLg@mail.gmail.com>
References: <CAPXaUT5D1DDa0zfAu_Ja7eZeage0MNhv4nCw=H9yW3w5nHM8tg@mail.gmail.com>
	<1464618022.104763.1464133950046.JavaMail.yahoo@mail.yahoo.com>
	<CAN4YXvfA=rYxFEwnqWi9J9kUSMykBe=kQ9+E7DSpE4nXkNEXAA@mail.gmail.com>
	<CAPXaUT48kvtQ1r=yMDZCg_6mCVQCCQXrsmzWKMkh97JotARTLg@mail.gmail.com>
Date: Wed, 25 May 2016 20:40:16 -0700
Message-ID: <CAPXaUT53E12UZBh9yEzjNYoZcFp+pHNHPL+EB4t2+Dm-KtEMNQ@mail.gmail.com>
Subject: Re: debugging solr query
From: Jay Potharaju <jspotharaju@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=001a113d30b270d83a0533b68c40
archived-at: Thu, 26 May 2016 03:40:23 -0000

--001a113d30b270d83a0533b68c40
Content-Type: text/plain; charset=UTF-8

Any links that illustrate and talk about solr internals and how
indexing/querying works would be a great help.
Thanks
Jay

On Wed, May 25, 2016 at 6:30 PM, Jay Potharaju <jspotharaju@gmail.com>
wrote:

> Hi,
> Thanks for the feedback. The queries I run are very basic filter queries
> with some sorting.
>
> q:*:*&fq=(dt1:[date1 TO *] && dt2:[* TO NOW/DAY+1]) && fieldA:abc &&
> fieldB:(123 OR 456)&sort=dt1 asc,field2 asc, fieldC desc
>
> I noticed that the date fields(dt1,dt2) are using date instead of tdate
> fields & there are no docValues set on any of the fields used for sorting.
>
> In order to fix this I plan to add a new field using tdate & docvalues
> where required to the schema & update the new columns only for documents
> that have fieldA set to abc. Once the fields are updated query on the new
> fields to measure query performance .
>
>
>    - Would the new added fields be used effectively by the solr index
>    when querying & filtering? What I am not sure is whether only populating
>    small number of documents(fieldA:abc) that are used for the above query
>    provide performance benefits.
>    - Would there be a performance penalty because majority of the
>    documents(!fieldA:abc) dont have values in the new columns?
>
>
> Thanks
> Jay
>
> On Tue, May 24, 2016 at 8:06 PM, Erick Erickson <erickerickson@gmail.com>
> wrote:
>
>> Try adding debug=timing, that'll give you an idea of what component is
>> taking all the time.
>> From there, it's "more art than science".
>>
>> But you haven't given us much to go on. What is the query? Are you
>> grouping?
>> Faceting on high-cardinality fields? Returning 10,000 rows?
>>
>> Best,
>> Erick
>>
>> On Tue, May 24, 2016 at 4:52 PM, Ahmet Arslan <iorixxx@yahoo.com.invalid>
>> wrote:
>> >
>> >
>> > Hi,
>> >
>> > Is it QueryComponent taking time?
>> > Ot other components?
>> >
>> > Also make sure there is plenty of RAM for OS cache.
>> >
>> > Ahmet
>> >
>> > On Wednesday, May 25, 2016 1:47 AM, Jay Potharaju <
>> jspotharaju@gmail.com> wrote:
>> >
>> >
>> >
>> > Hi,
>> > I am trying to debug solr performance problems on an old version of
>> solr,
>> > 4.3.1.
>> > The queries are taking really long -in the range of 2-5 seconds!!.
>> > Running filter query with only one condition also takes about a second.
>> >
>> > There is memory available on the box for solr to use. I have been
>> looking
>> > at the following link but was looking for some more reference that would
>> > tell me why a particular query is slow.
>> >
>> > https://wiki.apache.org/solr/SolrPerformanceProblems
>> >
>> > Solr version:4.3.1
>> > Index size:128 GB
>> > Heap:65 GB
>> > Index size:75 GB
>> > Memory usage:70 GB
>> >
>> > Even though there is available memory is high all is not being used ..i
>> > would expect the complete index to be in memory but it doesnt look like
>> it
>> > is. Any recommendations ??
>> >
>> > --
>> > Thanks
>> > Jay
>>
>
>
>
> --
> Thanks
> Jay Potharaju
>
>


-- 
Thanks
Jay Potharaju

--001a113d30b270d83a0533b68c40--