[
https://issues.apache.org/jira/browse/LUCENE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756432#action_12756432
]
Thomas Becker commented on LUCENE-1911:
---------------------------------------
Thanks for the patch. Issue can be closed I guess.
Attached you'll find a hotspot list for the same request with a patched
2.9-RC4. With the old api it's as fast as 2.4. Maybe a tad faster. With the new
api it's a bit slower. Most probably due to not caching sorted resultsets
anymore in our implementation.
Great work guys. Nice patch @Uwe. And big thanks for your support.
Was a pleasure. Now it's time to find a way to contribute something back to the
community.
> When using QueryWrapperFilter with CachingWrapperFilter, QueryWrapperFilter
> returns a DocIdSet that creates a Scorer, which gets cached rather than a bit
> set
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-1911
> URL: https://issues.apache.org/jira/browse/LUCENE-1911
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Mark Miller
> Assignee: Uwe Schindler
> Fix For: 2.9
>
> Attachments: LUCENE-1911.patch, LUCENE-1911.patch, LUCENE-1911.patch,
> LUCENE-1911.patch
>
>
> there is a large performance cost to this.
> The old impl for this type of thing, QueryFilter, recommends :
> @deprecated use a CachingWrapperFilter with QueryWrapperFilter
> The deprecated QueryFilter itself also suffers from the problem because its
> now implemented using a CachingWrapperFilter and QueryWrapperFilter.
> see
> http://search.lucidimagination.com/search/document/7f54715f14b8b7a/lucene_2_9_0rc4_slower_than_2_4_1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
