You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2010/01/11 16:28:54 UTC

[jira] Commented: (JCR-2461) Item retrival inefficient after refresh

    [ https://issues.apache.org/jira/browse/JCR-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798690#action_12798690 ] 

Michael Dürig commented on JCR-2461:
------------------------------------

The slow down is caused by merging changes of item states from the server with the local ones on the client. The main contribution seems to come from diffing the property states. 



> Item retrival inefficient after refresh
> ---------------------------------------
>
>                 Key: JCR-2461
>                 URL: https://issues.apache.org/jira/browse/JCR-2461
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 1.5.7
>            Reporter: Michael Dürig
>            Priority: Minor
>
> When RepositoryService#getItemInfos() returns a sufficiently large batch for a path, then the second invocation of getItem() below is significantly slower than the first. 
> String path = ...
> Item i = session.getItem(path);
> i.refresh(false); // same for refresh(true)
> session.getItem(path);
> In my test setup RepositoryService#getItemInfos() returns 3946 elements. The first invocation takes approx. 800ms, the second 3000ms.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.