The amount of data, both disk space and database rows, that is saved by LiveCycle can build over time. Sooner or later the LiveCycle administrator will probably find himself having to clean up and get rid of old, unused, completed, long-lived processes.
The CRX repository stores its data in tar files. Data is not overwritten or deleted as it is changed. The changed data is added to the tar files and older data continues to exist in the tar files, unused. Doing this makes the repository much more efficient. But this means that even small changes, if there are enough of them, will cause the amount of data residing in the jar files to become quite large.
How can the amount of space taken up by the repository’s tar files be quickly reduced?
CRX has functionality that works like memory garbage collection except for tar files. The tar files can be optimized with this functionality and reduced in size. When this happens the unused data stored in the tar files will be removed and the amount of data stored in the tar files can become much less. By default, this optimization occurs in the early morning hours. If the size of the repository tar files becomes too large the optimization can be run manually any time it is needed.
Running the CRX respository tar file optimization
After logging into the Experience Services console with an administrator account select the link, Repository Management, on the right. This will take you to the management screen for the CRX repository. Select the link, Tar Persistence Manager Optimization.
On this screen is a field, Delay after optimizing one transaction. Changing this to be a higher number will cause the optimization to take longer while using less of the processor on the server.
To optimize the tar files of the repository, press the button, Start Optimization. While this is running you will see two buttons, Refresh and Stop Optimization. To get updates of the progress of the optimization you will need to press the Refresh button. When completed, a message is displayed: Optimization successfully finished.
For more information see:
Documentation for CRX Persistence Managers