Tuning Performance of Unified Messaging

Note the following considerations when tuning performance of the UMS:

• Message type definitions are stored in an object manager-level cache. Messages are cached in memory and never written to the database. The Message Display list applet is based on a virtual business component that pulls data directly from the in-memory cache.

• Avoid using duplicate message suppression for business-to-business accounts. Duplicate suppression processing has to load all previous responses for the account at the beginning of the call. Loading more than 100 responses will result in a perceptible delay. If you must use duplicate message suppression in business-to-business situations, configure the message suppression to suppress duplicates by quote or by order instead of by account.

• Limit the number of messages displayed. It is generally accepted that the user will not view more than three or four recommendations at a time.

• Carefully consider the events that trigger the message-generation mechanism. In general, the message-generation mechanism will have a larger overhead than the UMS.