jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (JCR-2546) SISM blocks the item state cache when loading a new item
Date Mon, 08 Mar 2010 09:31:27 GMT

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

Jukka Zitting reopened JCR-2546:
--------------------------------


Marcel and Thomas noted that moving the synchronization from the cache to the SISM instance
may just relocate the problem. I think that this decoupling between itemExists() and getItem()
should still help, but will set up a test case to verify the actual gains.

> SISM blocks the item state cache when loading a new item
> --------------------------------------------------------
>
>                 Key: JCR-2546
>                 URL: https://issues.apache.org/jira/browse/JCR-2546
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 2.1.0
>
>
> The SharedItemStateManager.getNonVirtualItemState() method contains a loadItemState()
call within a "synchronized (cache)" block. This prevents all item state cache access while
a new item is being loaded from the persistence manager. I have at least one case where this
has caused a serious performance drop, essentially synchronizing repository access for all
readers.

-- 
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