could you provide more information? - which version of lucene.net you use - how many clauses have the query - how many time took the query without search - if you have read and applied all the points in the lucene performance faq (it's the one of the java version, but applies completely to the .net version) - do you optimize the index before doing the query - with how much frequency you reopen the indexreader.
without that is very difficult to make a guess of what can be happen. -- Jokin On Feb 6, 2008 8:21 AM, Nitin Shiralkar (JIRA) <[EMAIL PROTECTED]> wrote: > 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. > >
