[
https://issues.apache.org/jira/browse/LUCENENET-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558298#action_12558298
]
Erich Eichinger commented on LUCENENET-107:
-------------------------------------------
> Should there be a new method or parameter forcing not to cache the terms
Digy: Yes, I think there should be. At least in our website projects here,
we're using heavy concurrent Reader / Writer scenarios. Taking this a bit
further, it's maybe a good idea to introduce some kind of parameter-profile for
tuning Lucene for certain usage scenarios. Users then could easily select from
"readonly", "mostly read/few writes", "read/write equal", ... profiles.
> Search while sorting is slow
> ----------------------------
>
> Key: LUCENENET-107
> URL: https://issues.apache.org/jira/browse/LUCENENET-107
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Lucene.Net 2.1
> Reporter: Digy
> Attachments: TestSort.rar
>
>
> Mark wrote:
> "
> I have an index that when i search for term with out sorting the results are
> returned in .7 seconds or less. When I choose to search with a column chosen
> for sorting the results will return in 7 - 10 seconds. The larger the # of
> hits the longer it takes when sorting. The fields that can be sorted on are
> unique to the document,stored in the index as un_tokenized. I am using
> lucene.net 2.0. Index size is normally around 2.5 gig but i have the same
> problem on a 500 meg index too. Has anyone else experienced this?
> Any help will be greatly appreciated.
> Thanks,
> Mark Burks
> "
> I have prepared a test case where TestIndex contains ~200000 docs.
> a) making a search and then sorting the (500)results (I used SortedDictionary
> for sorting) takes ~140 msec.
> b) making a search with Lucene's Sort takes ~6046 msec.
> So, there is something to be fixed in Lucene.Net
> DIGY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
