jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] Resolved: (JCR-2461) Item retrieval inefficient after refresh
Date Wed, 24 Feb 2010 14:52:27 GMT

     [ https://issues.apache.org/jira/browse/JCR-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dürig resolved JCR-2461.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0
         Assignee: Michael Dürig

The fix to JCR-2498 should also fix this issue

> Item retrieval 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
>            Assignee: Michael Dürig
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: JCR-2461.patch
>
>
> 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.


Mime
View raw message