As far as JCR optmizations go:
I have been able to improve the performance on the CMS significantly by integrating a
cluster-aware JBoss Cache based PersistenceManager.
However, I have noticed that Jackrabbit maintains an in-memory cache that does not support
clustering. It is critical to make this cache cluster aware if the content publishing (CMS
Admin Tool) was to be cluster aware/safe.
I am starting to look at the Jackrabbit codebase, and couple of options come to mind:
1) Disable the internal cache completely. (Julien mentioned some issues with cache
listeners in JackRabbit). this will have to be inverstigated further
2) Fork some jackrabit code to integrate a JBossCache based impl instead of their
non-clustered approach (Same issue with cache listeners can be a problem)
3) More long term and best option, have our own implementation of JCR spec with cluster
design taken into account from the beginnning
Thanks
Sohil
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969134#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...