Truncating data is a CPU-intensive activity that involves the interaction of the RAPCache database with the Operations Console, the RAPCache database Job Scheduler, and processes created by the RAPCache database Job Scheduler.
To increase truncation performance, create the appropriate user-defined execution classes, use the component application name to associate the execution class with the component, and assign one or more dedicated engines to each execution class.
| Description | Component | Component application name | Recommended number of dedicated engines |
|---|---|---|---|
| A user-defined execution class to improve the performance of adding transfer and truncation rules into the system and checking the cache for cache-full based rules.
Note: Create only one user-defined execution class to improve the performance of both transfer and truncation rules.
|
Operations Console | operationsconsole | Associate a minimum of one and and a maximum of (number of unused engines available in the system) dedicated engines with the user-defined execution class. |
| A user-defined execution class to improve the performance of the RAPCache database Job Scheduler to handle requests from the Operations Console for creating one or more internal processes for processing transfer and truncation rules.
Note: Create only one user-defined execution class to improve the performance of both transfer and truncation rules. Additionally, define this execution class only if the RAPCache database performance monitoring tools indicate that the JSAgent application is a point of contention in the system.
|
RAPCache | JSAgent | Associate a minimum of one and a maximum of (number of unused engines available in the system) dedicated engines with the user-defined execution class. |
| A user-defined execution class to improve the performance of the internal processes created by the RAPCache database Job Scheduler for processing the transfer and truncation rules.
Note: Create separate user-defined execution classes to improve the performance of transfer and truncation rules since the recommended engine allocation for the two activities differ significantly.
|
RAPCache |
JSAgent - <username> where <username> is the name used to connect to the RAPCache database that is associated with the rule.
Note: Sybase recommends that you use different database user accounts for transfer and truncation rules to further enhance system performance. For example, if a user name of RAP_USER is connecting to the database for transfer rules, use a user name of RAP_DELETE for the truncation rules.
|
Associate a minimum of one and a maximum of (number of concurrent truncation rules executing x the number of partitions per table from which the data is being deleted) dedicated engines with the user-defined execution class. |