For merge, revert, and check-in operations that involve a large number of assets, ATG Content Administration automatically uses optimization features to improve database performance. When optimization is disabled, these operations iterate over workspace assets and issue SQL statements for each one. When optimization is enabled, a single SQL operation is performed on all workspace assets.
By default, the threshold number of workspace assets required to trigger an optimized operation is set to 500. To change this number, set the following VersionManagerService properties to an integer value:
mergeOptimizationThresholdCountrevertOptimizationThresholdCountworkspaceOptimizationThresholdAssetCountspecifies the minimum number of workspace assets required to trigger optimized check-in.
You can set these properties to the same or different values. To ensure optimization for a given operation, set the corresponding property to 0.
Note: For Oracle, the setting for mergeOptimizationThresholdCount works only if the database does not contain LONG datatype columns. To enable merge optimization, change the following column datatypes: LONG or LONG VARCHAR to CLOB, and LONG RAW to BLOB.
Optimized operations require table joins and invalidation of GSA caches. Thus, optimization settings can enhance performance for large loads but might adversely affect performance for small loads.
To disable optimized merge or revert, set two VersionManagerService properties to false:
useOptimizedReplicationForMergeuseOptimizedReplicationForRevert
