Performance Tuning for Content Manager

90 Performance Tuning for Content Manager

by different people. At each workflow step, this document is viewed by the

person performing the activity. This example means that each form is

retrieved at least seven times. That does not seem like much, but if there are

10,000 of these forms arriving each day, then there are 70,000 retrievals

happening each day.

4.3 Translating current processes to the new data model

When sizing the system, first you must determine what item types will make up

the system. This can be the most difficult task in sizing the system. You need to

understand how the customer currently uses these documents, and how the

customer wants to conduct business with the Content Manager system.

Develop the data model that will define the documents as item types and describe

what attributes and objects the documents have. If folders or links are to be used,

determine what they represent to the business and how they fit into the process.

When choosing attributes for your item types, your primary concerns are

identifying data that will be searched, and fields that will distinguish one

document from another when a list of search results are displayed. When a user

looks for an item in the system, what information about that item does the user

already have? In a customer service application, when a customer initiates a

query, does the customer already have a customer number, a reference number,

or just the customer name? Is there a need to search by the date sent, received,

processed, published, or a combination of the values?

Remember that the Library Server tables (specifically the item type root

component or child component tables) will have a column for every key field

defined, and there will be one row in the root component table for every item in

the item type, and possibly many rows in the child component table or tables.

Avoid having an attribute for every thing you can think of attached to each item.

Although you might want everything about the item to be used for searching, it

could lead to masses of unnecessary data on the Library Server and, as a

consequence, increased search times and more data to back up and maintain.

4.4 Analyzing the impact of a new workload

Every action that is performed by a client talking to a Library Server uses some

small amount of the resources of the Library Server. The key to estimating the

total load on the server is to estimate the total number of actions the client

community must perform to support the customer’s business requirements. For

instance, if you create 10,000 documents per day, that is 10,000 store requests