Performance Tuning for Content Manager

130 Performance Tuning for Content Manager

SMS fills each volume assigned to a storage class in a storage group, then

moves to the next volume. This means that if you have multiple disk volumes

dedicated to a storage class in a workstation collection, each volume will be filled

in turn. SMS enables you to share disk volumes between storage groups and

workstation collections, so that items from multiple workstation collections can

exist on the same disk volumes. To spread the workload over the disk drives, you

should dedicate the drives to a particular workstation collection. If you need to

share them, create multiple storage groups and change the order in which the

volumes are defined.

Space-based migration

Content Manager Version 8.2 enables you to define migration according to

capacity as well. Setting a volume threshold below 100% will cause the migrator

to monitor the volume’s free space and potentially move data before the

migration policy predicts. If you are using migration and you have a good

understanding of the usage patterns, set this value to 100% and use overflow

volumes to avoid running out of storage.

Alternatively, if you wish to keep as much data on the Content Manager managed

disk as possible, set the migration period long (but not forever) and the volume

capacity threshold below 100%. Define a next storage class in the migration

policy as the destination for resource items when they are eventually migrated.

The migration period for the Content Manager disk storage class (or classes) can

be set long enough that any access after this time is very unlikely. Resource

objects will be on disk for this period and get fast access. Set the migration

thresholds on the volumes for the Content Manager managed disk under 100 %

to avoid running out of space. The resource items will reside on disk for up to the

migration period, as long as you might possibly need them, unless you begin to

run out of disk capacity before the migration period. The volume threshold will

become the trigger for migration; old data will move to the next storage location,

maintaining some free space on disk for your new data.

5.6.4 Logging

There is a Resource Manager activity log file as well, but it is not controlled by the

administration panels. The method and detail recorded in this log is specified in

the icmrm_logging.xml file, which is located in the following directory:

.../Websphere/AppServer/installedApps/<node name>/<Resource Manager

name>.ear/icmrm.war/

In this syntax:

 <node name> is the WebSphere Application Server node name. This is

usually the server host name.