Tuning Bedework

Database Caching and Hibernate

The performance of your system is likely to be very dependent upon the caching strategies used. For small to medium deployments the default settings may be perfectly adequate.

For large systems you may need to spend some time reading the documentation available at the Hibernate site and the sites of the various cache implementors.

Bedework allows different cache regions for each application type. This allows the deployer to adopt aggressive caching strategies fro the public events clients for example, while having less caching or much shorter flushing intervals for personal clients where immediate visibility of changes is necessary.

There are two parameters in the bwbuild/myconfig/cal.options.xml file which affect caching. The default settings are

          <cachingOn>true</cachingOn>

          <cachePrefix>bwpubevents</cachePrefix>

These settings turn caching on and set the cache prefix to “bwpubevents”. This is used in the ehcache settings file to distinguish cache settings.

The default cache for Bedework is currently Ehcache. The latest versions of this cache do allow clustering. Other caching schemes are available such as the Jboss cache. The Hibernate site offers details on the alternatives.

Setting JVM Parameters

See "Reviewing JVM parameters"