[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher Zimmermann updated MAGNOLIA-3905:
---------------------------------------------

    Fix Version/s: 5.0
                       (was: 5.0 Alpha1 s010)

> Remove usage of ExclusiveWrite
> ------------------------------
>
>                 Key: MAGNOLIA-3905
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3905
>             Project: Magnolia
>          Issue Type: Task
>      Security Level: Public
>          Components: core
>            Reporter: Fabrizio Giustina
>            Assignee: Daniel Lipp
>            Priority: Major
>             Fix For: 5.0
>
>
> Performances of concurrent editing in Magnolia is highly affected of the 
> global sinchronization on ExclusiveWrite, expecially due to the usage in 
> SaveHandlerImpl.
> ExclusiveWrite was more a quick and dirty hack than a solution to concurrency 
> implemented years ago. The main reason why it's bad is that is global: no 
> matter which node you are saving or which repository you are working on, you 
> will hold a lock which will block any other dialog from saving. That means 
> that also saving a document to the dms or anything else into the data module 
> is actually locking the whole system for editing.
> A second reason why it's bad: it has totally no effect on clustered 
> instances, since it's local to a single Magnolia instance. IF the problem 
> it's trying to fix is concrete, synchronization should be done on a 
> repository level, not at instance level.
> A good approach would be using jcr locks on nodes (locking works also with a 
> clustered repository).
> Since Magnolia actually uses a "soft locking" approach everywhere, by 
> allowing concurrent editing assuming that concurrent save operation on the 
> same node would be really limited, my suggestion is to simply get rid of the 
> synchronization block in SaveHandlerImpl, without introducing addictional 
> checks at the moment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to