Performance Considerations While Running Purge

While running, purge uses significant resources from the database, cache, and text index.

While you can continue to use the system, the TIBCO MDM may appear sluggish. When data is removed from the database, the database updates all indexes.

Purge consumes a large amount of database resources and therefore may negatively affect performance. To avoid this, schedule purges to coincide with periods of low or no activity and also schedule only one purge job at a time. If you run a purge for the first time or after a long period after the last purge, it may take more time to complete than a regularly scheduled purge.

If you are running a purge for a repository (to clean up all records), performing an import for the same repository can generate resource contention and deadlocks. This can significantly slow the purge and import process.

Copyright © Cloud Software Group, Inc. All rights reserved.