lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Shiralkar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENENET-109) Severe search performance drop in case of sorting on ID fields
Date Fri, 08 Feb 2008 06:31:10 GMT

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

Nitin Shiralkar commented on LUCENENET-109:
-------------------------------------------

Ok. We have some design issues in our system not allowing us to use the same instance. But
then why is that not a problem while sorting on other fields? Is there any other workaround
available?

> 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.


Mime
View raw message