Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-9709

New VCS CachingMapper implementation using ehcache

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.7.2
    • Component/s: Core VCS
    • Tags:
    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      To activate the cache, it must be added in the default-repository-config.xml that is used (usually from a template):

      <cachingMapper enabled="true" class="org.nuxeo.ecm.core.storage.sql.UnifiedCachingMapper">
      <property name="ehcacheFilePath">/opt/vcs-ehcache.xml</property>
      </cachingMapper>

      Then an Ehcache configuration file (/opt/vcs-ehcache.xml in the example) must be provided.

      There are two possible examples for this file (see ticket comments):

      • one for XA, which provides the same transaction isolation semantics as the default cache (READ COMMITTED),
      • one without XA, which provides a transaction isolation of READ UNCOMMITTED but is faster.
        In any case the Ehcache configuration must be tuned the expected or measured usage, especially sizing and disk spill off.

      When starting with this cache the logs contain:
      INFO [UnifiedCachingRowMapper] Creating ehcache manager for VCS, using ehcache file: /opt/vcs-ehcache.xml

      This cache can be monitored using JMX, under the root "net.sf.ehcache".

      Show
      To activate the cache, it must be added in the default-repository-config.xml that is used (usually from a template): <cachingMapper enabled="true" class="org.nuxeo.ecm.core.storage.sql.UnifiedCachingMapper"> <property name="ehcacheFilePath">/opt/vcs-ehcache.xml</property> </cachingMapper> Then an Ehcache configuration file (/opt/vcs-ehcache.xml in the example) must be provided. There are two possible examples for this file (see ticket comments): one for XA, which provides the same transaction isolation semantics as the default cache (READ COMMITTED), one without XA, which provides a transaction isolation of READ UNCOMMITTED but is faster. In any case the Ehcache configuration must be tuned the expected or measured usage, especially sizing and disk spill off. When starting with this cache the logs contain: INFO [UnifiedCachingRowMapper] Creating ehcache manager for VCS, using ehcache file: /opt/vcs-ehcache.xml This cache can be monitored using JMX, under the root "net.sf.ehcache".

      Description

      Since NXP-9574 caching mapper is pluggable, the idea is to have a unified cache using ehcache (instead of a softref map by connection).

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.