![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Default is false. If set to false: When a rule action changes the value of an entity’s properties, then the entity instance is evicted from the cache instead of updating it. Updates are saved in the backing store. Use this setting and Agent.AgentClassName.threadcount as needed to improve performance and cache memory management.See CDD Cluster Tab Domain Objects Default Settings Reference for details on the Evict From Cache on Update setting. Agent.AgentClassName.threadcount For use with cache aside and only when parallel operations feature is used (see Agent.agentClassName.enableParallelOps).Defines the number of $CacheWriter threads performing cache writing jobs.See Chapter 10, Threading Models and Tuning in TIBCO BusinessEvents Architect’s Guide for usage guidelines.Tip This property is also used to define the number of Recovery threads (used for recovering Cache Plus Memory entity handles at inference engine startup). Note For use with cache aside and only when the parallel operations feature is used.For a guide to usage, see the section Database Write Tuning Options for Cache Aside in Chapter 10, Threading Models and Tuning in TIBCO BusinessEvents Architect’s Guide. Agent.agentClassName.enableParallelOps If true, parallel operations are used Post-RTC phase operations are done in parallel:
• If false, sequential operations are used All post-RTC phase operations are done on a single thread in the order shown above. Agent.AgentClassName.dbthreadcount Defines the number of database write threads available to process the RTC transactions from the queue, that is, the number of threads performing database writing jobs ($DBWriter thread pool). Writes include applying entity inserts, updates, and deletes to the database.Although the limit is seldom reached, you can guarantee that a connection is always available for a dbwriter thread as follows. Set this field to the same value as CDD Cluster tab > Backing Store > Connection > Max Size field. Agent.AgentClassName.dbOpsQueueSize Note When the queue is full, all engine operations are blocked. Agent.AgentClassName.dbOpsBatchSize Database write threads process the RTC transactions from the queue. The number of threads is defined by dbthreadcount.A database write thread takes up to the dbOpsBatchSize number of RTC transactions, processes them and commits them to the database. (When database write threads are idle, they take available jobs from the database operations queue, even if there are less jobs than dbOpsBatchSize.) Default is false. be.engine.cacheServer.channel.disable
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |