Purge Performance Recommendations
The purge process removes data from the live database tables.
| Recommendation | Comments |
|---|---|
Purge business processes |
The Schedule_IndexBusinessProcessService runs every 10 minutes. By default, it is configured to index 5,000 business processes every time it runs, which translates to 720,000 business processes in a 24-hours time span. If your system is
handling a high volume of business processes, you can increase the
number of business processes indexed per cycle. You can modify the
Schedule_IndexBusinessProcessService business process by modifying
variable as shown in the following example:
|
Batch purge |
The Schedule_PurgeService scans the ARCHIVE_INFO
database table to purge data in the system. By default, it purges
2,000 rows of data in batches to limit the database transaction size.
You can set the batch size in the jdbc_purge.propeties file that can
be located in install_dir/install/properties (install_dir\install\properties for Windows) directory. Modify the
batch size by changing the variable as shown in the following example:
Note: Replace
the database_name with the
database you are using along with Sterling B2B Integrator, for example,
mssql.
If you modify the value to increase the batch purge rate, ensure that you configure your database with sufficient log space to handle large transactions. |
Document lifespan |
By default, lifespan for information persisted by a business process is two days. The Schedule_PurgeService purges data in competition with business activity on a system with predictable processing periods. You can defer document lifespan by increasing the business process lifespan. For example, consider that the system is processing information from 8 a.m. to 5 p.m., you can increase the document lifespan by 12 hours, the purge activity will occur between 8 p.m. on the same day and 5 a.m. on the next day. You can modify the business process lifespan by logging in as a Sterling B2B Integrator administrator. Navigate to and perform the changes. |
Database compression |
The Schedule_IndexBusinessProcessService
and the Schedule_PurgeService runs complex queries which results
in signification disk I/O on the database server. You can compress
the database tables provided in the following list to achieve significant
reduction (up to 50% in some cases) in disk usage:
|