You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2013/11/30 15:16:49 UTC
[jira] [Reopened] (SOLR-1927) DocBuilder Inefficiency
[ https://issues.apache.org/jira/browse/SOLR-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson reopened SOLR-1927:
----------------------------------
> DocBuilder Inefficiency
> -----------------------
>
> Key: SOLR-1927
> URL: https://issues.apache.org/jira/browse/SOLR-1927
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.4
> Reporter: Robert Zotter
> Priority: Trivial
> Labels: DIH, DocBuilder
> Attachments: SOLR-1927.patch
>
>
> I am looking into collectDelta method in DocBuilder.java and I noticed that
> to determine the deltaRemoveSet it currently loops through the whole
> deltaSet for each deleted row.
> Does anyone else agree with the fact that this is quite inefficient?
> For delta-imports with a large deltaSet and deletedSet I found a
> considerable improvement in speed if we just save all deleted keys in a set.
> Then we just have to loop through the deltaSet once to determine which rows
> should be removed by checking if the deleted key set contains the delta row
> key.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org