CDD Cluster Tab Domain Objects Default Settings Reference
The Domain Object Default settings apply to all objects except those for which you explicitly configure overrides, using the Domain Object Overrides section.
See CDD Cluster Tab Domain Object Override Settings Reference.
Property | Notes |
---|---|
Mode | |
With Cache OM, you can keep memory objects in the cache or Rete network using the following cache modes.
|
|
Preload Entities | |
Specifies whether objects are loaded into the cache from the backing store on system startup (both normal startup and recovery).
|
|
Preload Handles | |
Specifies whether object handles are loaded into the
ObjectTable cache. The
ObjectTable cache holds references (handles) to the objects themselves.
Handles are used in the object table.
|
|
Preload Fetch Size | |
If
Preload Entities or
Preload Handles or both are checked, this setting specifies the number of entity objects or handles (or both) to preload for each entity type whose objects or handles (or both) are configured to be preloaded.
This setting applies to both objects and handles and cannot be set differently for each. Objects and handles are fetched in a non-deterministic manner. This setting can be overridden at the entity level. Set to 0 to preload all. Set to a number to load that number of objects or handles (or both). Default is 0. Ignored unless Preload Entities or Preload Handles or both are checked. |
|
Check for Version | |
This field applies to concepts that use cache-only mode or cache+memory mode.
An inference agent uses its L1 cache, a local cache of limited size, to improve access time to the concepts stored in the cluster cache. When an agent finds a concept instance in this local cache, the Check for Version setting determines whether the agent will use the instance directly, or instead check in the cluster cache for more recent version.
|
|
Constant | |
This field applies to entities that use the cache-only mode or the cache+memory mode. In multi-engine deployments, use only for entities that do not change after creation.
The processing unit has a special local cache used only for entities marked as Constant. Entities placed in this cache are only removed when they are explicitly deleted. If the processing unit finds an entity in the constant cache, it will use it without checking in the cluster. |
|
Evict from Cache on Update | |
Used only if both of the following are the case:
|
|
Is Cache Limited | |
If checked, the cache size is limited.
Limited cache requires use of a backing store. See Configuring a Limited (or Unlimited) Cache . The size of the entity cache and the size of the object table cache are set in the Object Management section of the Cluster tab. If not checked, the cache size is unlimited. You can override this default setting in entity overrides. Default is unchecked. |
|
Subscribe Cluster | |
For objects that use Cache+Memory mode, check this checkbox to subscribe to subscription RTCs, so that changes to this object in one Rete Network are also changed in the Rete networks across all inference agents.
Default is checked. |