Database Write Queue and Thread Pool (Agent Level)
Actions for one or more RTCs are done in one or more batches, depending on tuning options.
In each batch, TIBCO BusinessEvents does the following actions (as needed):
deleteConcepts deleteEvents insertConcepts insertEvents modifyConcepts removeObjectTable saveObjectTable
You can tune each agent’s database write behavior using the following options:
Agent.AgentClassName.dbOpsQueueSize Agent.AgentClassName.dbOpsBatchSize Agent.AgentClassName.dbthreadcount
The post-RTC database (backing store) transactions are queued into a database-operations queue whose maximum size (set per agent) is defined by dbOpsQueueSize. Each slot in the queue contains all the actions from one RTC.
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.)
You can monitor JMX parameter AvgDBOpsBatchSize to see the effective value used in your use case.