[jboss-dev-forums] [Design of JBoss Portal] - Re: Portal 2.4.1

[sohil.shah@jboss.com]

anonymous wrote : 
  | 1) Is disabling jackrabbit's in-memory cache an option from performance perspective? Is it a config or source code change?
  | 

Currently, this is a source code change. 

Yes. if we have our JBossCache based PersistenceManager layer, caching in the jackrabbit layer is actually redundant. The performance boost will be unaffected and we have a fully clustered CMS instead of requiring a singleton cluster node for CMS administration functions


anonymous wrote : 
  | 2) http://issues.apache.org/jira/browse/JCR-169 was supposed to provide hooks for distributed cache, but it doesn't seem like this will be done by jackrabbit developers soon. Is it a possibility to just implement a hook for external cache and give it to jackrabbit? Then we could integrate it with JBossCache without having to fork jackrabbit. 
  | 

This shouldn't be a bad strategy. Definitely more preferable to forking jackrabbit codebase. 

anonymous wrote : 
  | 3) 3.0 timeframe?
  | 

I am hoping to squeeze the performance boost by using a JBossCache PersistenceManager immediately in the 2.4.1 release. The jackrabbit caching issue may have to be addressed after that depending on what strategy we pick for it.

I am looking at the jackrabbit codebase currently and see if something can be done for 2.4.1

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969335#3969335

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969335