lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-6878) TopDocs.merge should use updateTop instead of pop / add
Date Tue, 03 Nov 2015 14:30:28 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-6878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987350#comment-14987350
] 

ASF subversion and git services commented on LUCENE-6878:
---------------------------------------------------------

Commit 1712299 from [~jpountz] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1712299 ]

LUCENE-6878: Speed up TopDocs.merge.

> TopDocs.merge should use updateTop instead of pop / add
> -------------------------------------------------------
>
>                 Key: LUCENE-6878
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6878
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/search
>    Affects Versions: Trunk
>            Reporter: Daniel Jelinski
>            Assignee: Adrien Grand
>            Priority: Trivial
>         Attachments: LUCENE-6878.patch
>
>
> The function TopDocs.merge uses PriorityQueue in a pattern: pop, update value (ref.hitIndex++),
add. JavaDocs for PriorityQueue.updateTop say that using this function instead should be at
least twice as fast.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message