You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Digy (JIRA)" <ji...@apache.org> on 2008/02/06 16:29:08 UTC

[jira] Commented: (LUCENENET-109) Severe search performance drop in case of sorting on ID fields

    [ https://issues.apache.org/jira/browse/LUCENENET-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566158#action_12566158 ] 

Digy commented on LUCENENET-109:
--------------------------------


This happens mostly when the indexreader(indexsearcher) is reopened with every search.

DIGY

> Severe search performance drop in case of sorting on ID fields 
> ---------------------------------------------------------------
>
>                 Key: LUCENENET-109
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-109
>             Project: Lucene.Net
>          Issue Type: Bug
>            Reporter: Nitin Shiralkar
>
> Severe search performance drop in case of sorting on ID fields. I am using a lucene index where if I query for documents (500 result set) with sorting on document date field, then I get a resposne in ~2000 ms. However for the same query with sorting on Document Id field, then I get a response in ~4500 ms. This drop in search performance is even more severe on larger index.
> Lucene Index:
> 1. Document count: ~1000,000
> 2. Index size: > 8 GB
> Search Query:
> document_subtype:1.1201
> Lucene Search API:
> topDocs  = indexSearcher.Search (userQuery,  null, m_nMaximumRecordSetSize, sortField );

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.