Performance Tuning for Content Manager

Appendix A. Performance tuning guidelines for a Document Manager system 441

Additional optimization can be achieved through advanced configuration of the

Document Manager services. Lifecycle, Rendition, Print, and Notification service

can be configured to manage a specific subset of classes or configurations. The

system can be configured to handle specific loads of documents by class to help

balance workload and prioritize processing of designated document classes.

Action and dialogs

Options that are available in the actions and dialogs can increase performance

time for actions such as add and checkin. Scanning for compound documents,

incrementing revision number, checking for uniqueness, and applying unique

document numbers can all add a significant amount of time to these processes.

Consider these options and their impact before including them in your system

design. If these options are not required as part of your system, they should be

disabled to eliminate additional processing time for document operations.

General system considerations

Additional system configurations should be evaluated to keep your Document

Manager server running at optimum performance.

Sufficient drive space is required for the Document Manager server. If the

Document Manager server’s hard drive space is reaching its capacity, Windows

virtual memory will be swapped more frequently. This can contribute to a

sluggish response by the Document Manager server. Keeping system trace files

to verbose logging settings can contribute to the utilization of free disk space.

Although system trace files are useful in solving and identifying system problems,

provisions should be made to prevent these files from growing too large.

A high degree of drive fragmentation impedes performance.

Virus scanning programs can impact performance. Every document moved

either to or from the library repository is temporarily written to the Document

Manager server. Every one of those documents may be scanned by virus

software depending upon your scan interval settings.

Performance might be improved by the physical locations of the Document

Manager server, Library Server, and Resource Manager. Close proximity of

these systems can significantly improve performance. Co-locating these systems

geographically, on the same Windows domain, or on the same subnet will

improve system performance.

442 Performance Tuning for Content Manager

A DNS server can affect performance if it becomes unavailable or experiences

problems. If the DNS is used to reference machine names, the Document

Manager server will have problems locating systems if the DNS server is

unavailable.

ODBC drivers on the Document Manager server should be up to date.

Document Manager services are often configured to run as either local or

domain Windows accounts. Working with your IT group to ensure their

understanding of these accounts and their security requirements helps prevent

problems such as disabled or expired accounts.