jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-1892) OrderedIndexConcurrentClusterIT takes too long
Date Thu, 10 Jul 2014 10:34:04 GMT

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

Michael Dürig commented on OAK-1892:
------------------------------------

bq. Committed in http://svn.apache.org/r1607362 an average of 17-18% improve on insert after
code clean-up based on running

Trying this out with a big content package install I've seen a lot of time spent in {{OrderedContentMirrorStoreStrategy}}
and the process running for more then half an hour (at which point I lost patience). The problem
is caused by the many calls to {{NodeBuilder#getNodeState}}. That call is not particular efficient
as it caused a fresh snapshot of the current builder state to be taken every time. It is particular
costly if there are many changes to the builder. 

> OrderedIndexConcurrentClusterIT takes too long
> ----------------------------------------------
>
>                 Key: OAK-1892
>                 URL: https://issues.apache.org/jira/browse/OAK-1892
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>         Environment: trunk and 1.0 branch
>            Reporter: Marcel Reutegger
>            Assignee: Davide Giannella
>         Attachments: benchmarks - OAK-1892.csv
>
>
> The OrderedIndexConcurrentClusterIT takes too long and times out on travis. See e.g.
https://travis-ci.org/apache/jackrabbit-oak/builds/27445383



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message