Cisco Cisco Workload Automation 6.3 Referencia técnica
37
Tuning CWA
Configuration and Tuning
RemoteMasterServer.MaxSessionPoolSize (5)
RemoteMasterServer.MaxConcurrentMessages (5)
The following tes-6.0.dsp properties are what you would tune for Master to DSP message traffic:
ClientNode.MinSessionPoolSize (5)
ClientNode.MaxSessionPoolSize (10)
ClientNode.MaxConcurrentMessages (10)
The following tes-6.2.dsp properties are what you would tune for Fault Monitor to DSP message traffic:
FTNode.MinSessionPoolSize (2)
FTNode.MaxSessionPoolSize (5)
FTNode.MaxConcurrentMessages (5)The following tes-6.2.dsp properties are what you would tune for Cache Read
connections shared among all threads:
connections shared among all threads:
DataCache.ReadConnectionsMin (2) – minimum number of JDBC connections kept pooled to read from the data
cache. Having connections always available to handle read requests reduces the cost of allocating connections on
demand.
cache. Having connections always available to handle read requests reduces the cost of allocating connections on
demand.
DataCache.ReadConnectionsMax (4) – maximum number of JDBC connections allowed to be allocated concurrently
to read from the data cache. If this number is exceeded, read requests will be queued and blocked. Recommend
increasing to handle more concurrent users.
to read from the data cache. If this number is exceeded, read requests will be queued and blocked. Recommend
increasing to handle more concurrent users.
The following tes-6.2.dsp properties are what you would tune for Cache Write connections shared among all threads:
DataCache.WriteConnectionsMin (4) – minimum number of JDBC connections kept pooled to write to the data
cache. Having connections always available to handle write requests reduces the cost of allocating connections on
demand.
cache. Having connections always available to handle write requests reduces the cost of allocating connections on
demand.
DataCache.WriteConnectionsMax (8) – maximum number of JDBC connections allowed to be allocated concurrently
to write to the data cache. If this number is exceeded, write request will be queued and blocked. Recommend
increasing to handle more data update activity between the Master and DSP.
to write to the data cache. If this number is exceeded, write request will be queued and blocked. Recommend
increasing to handle more data update activity between the Master and DSP.
The following tes-6.2.dsp properties are what you would tune for Cache Tuning tradeoff between performance and
memory/disk usage:
memory/disk usage:
DataCache.PageCacheSize (50000) – number of pages (of size DataCache.PageSize) in memory allocated to the
data cache. The in-memory data cache allows for the fastest possible read/write access. Thus, for very large data
caches, it is recommended that the data cache be given as much memory as possible.
data cache. The in-memory data cache allows for the fastest possible read/write access. Thus, for very large data
caches, it is recommended that the data cache be given as much memory as possible.
DataCache.PageSize (4096) – size (in bytes) of each page in the data cache. The data cache stores records in
page-size chunks. Larger pages may improve read/write access when the data cache needs to fetch records from
disk, with the added cost of a larger data cache in-memory and on disk. Another factor to keep in mind is the OS
disk block size. Usually, it is recommended to keep the data cache page size the same as the OS disk block size.
page-size chunks. Larger pages may improve read/write access when the data cache needs to fetch records from
disk, with the added cost of a larger data cache in-memory and on disk. Another factor to keep in mind is the OS
disk block size. Usually, it is recommended to keep the data cache page size the same as the OS disk block size.
DataCache.CacheSizeDefault (1000) – number of objects each table in the data cache is allowed to keep in memory.
More objects equals faster read/write access from and to the data cache.
More objects equals faster read/write access from and to the data cache.
The following tes-6.2.dsp properties are what you would tune for Cache Syncing, which affects the data sync between
the Master database and Client Manager (DSP) cache.
the Master database and Client Manager (DSP) cache.
CacheSynchronizer.Purge (N) – Y to purge leftover deleted records during sync. Leftover records may exist in the
cache if the Master deletes the records from its database when the Client Manager is not connected.
cache if the Master deletes the records from its database when the Client Manager is not connected.