solr performance problem from 4.3.0 with sorting

[Ariel Zerbib <ar...@gmail.com>]

Hi,

We updated to version 4.3.0 from 4.2.1 and we have some performance
problem with the sorting.


A query that returns 1 hits has a query time more than 100ms (can be
more than 1s) against less than 10ms for the same query without the
sort parameter:

query with sorting option: q=level_4_id:531000000000000044&sort=level_4_id+asc
response:
        - <int name="QTime">1</int>
        - <int name="QTime">106</int>


query without sorting option: q=level_4_id:531000000000000024
        - <int name="QTime">1</int>
        - <result name="response" numFound="1" start="0">

the field level_4_id is unique and defined as a long.

In version 4.2.1, the performances were identical. The 4.3.1 version
has the same behavior than the version 4.3.0.

Thanks,
Ariel

Re: solr performance problem from 4.3.0 with sorting

[Shane Perry <th...@gmail.com>]

Ariel,

I just went up against a similar issue with upgrading from 3.6.1 to 4.3.0.
 In my case, my solrconfig.xml for 4.3.0 (which was based on my 3.6.1 file)
did not provide a newSearcher or firstSearcher warming query.  After adding
a query to each listener, my query speeds drastically increased.  Check
your config file and if you aren't defining a query (make sure to sort it
on the field in question) do so.

Shane

On Thu, Jun 20, 2013 at 3:45 AM, Ariel Zerbib <ar...@gmail.com>wrote:

> Hi,
>
> We updated to version 4.3.0 from 4.2.1 and we have some performance
> problem with the sorting.
>
>
> A query that returns 1 hits has a query time more than 100ms (can be
> more than 1s) against less than 10ms for the same query without the
> sort parameter:
>
> query with sorting option:
> q=level_4_id:531000000000000044&sort=level_4_id+asc
> response:
>         - <int name="QTime">1</int>
>         - <int name="QTime">106</int>
>
>
> query without sorting option: q=level_4_id:531000000000000024
>         - <int name="QTime">1</int>
>         - <result name="response" numFound="1" start="0">
>
> the field level_4_id is unique and defined as a long.
>
> In version 4.2.1, the performances were identical. The 4.3.1 version
> has the same behavior than the version 4.3.0.
>
> Thanks,
> Ariel
>