Performance Tuning Guide > Tuning Siebel Configurator for Performance >
Configuring Snapshot Mode Caching for Configurator
When Snapshot Mode memory caching has been configured for server-based Siebel Configurator deployments, when a user starts a configuration session, customizable products and related services may be loaded from the Snapshot Mode cache. Using Snapshot Mode can greatly improve performance for initializing configuration sessions.
If you do not use Snapshot Mode caching, then configuration sessions are subject to the behavior described in Default Caching Behavior for Configurator.
Snapshot Mode caches the following data:
- All objects associated with customizable product definitions
- A Model Manager (formerly Factory) instance for each customizable product
- A Worker instance for each user session
For more information about Siebel Configurator architecture elements such as Model Managers and Workers, see Product Administration Guide.
If an item is not in the Snapshot Mode cache, the item is retrieved from CFGCache, if it is verified to be the current version, and then added to the Snapshot Mode cache for subsequent use.
Using Snapshot Mode is highly recommended, particularly if you have large numbers of users.
Note the following behavior for configuration sessions for which Snapshot Mode is in effect:
- When a product administrator goes into validate mode, the workspace version of the customizable product is used rather than the version in the Snapshot Mode cache.
- When a product administrator releases a new version of a customizable product, the Snapshot Mode cache is marked. When a new user session tries to access the customizable product, the new version is loaded into the cache.
- When the size limit is reached for a Snapshot Mode cache, the oldest or least frequently accessed items are deleted. The Snapshot Mode cache contains the most recently or most frequently requested customizable product items.