1,126
edits
Difference between revisions of "Improving Content Manager OnDemand Performance"
Jump to navigation
Jump to search
Improving Content Manager OnDemand Performance (view source)
Revision as of 18:00, 10 February 2017
, 18:00, 10 February 2017Many tweaks to the article on IBM CMOD Performance.
m (Tweaked Link to Table Segmentation) |
(Many tweaks to the article on IBM CMOD Performance.) |
||
| Line 1: | Line 1: | ||
{{TOCright}} | {{TOCright}} | ||
It's possible to improve IBM CMOD's performance by paying close attention to configuration of Application Groups, Applications, and being careful with the usage of the CMOD utilities. | |||
= Introduction = | = Introduction = | ||
| Line 10: | Line 11: | ||
== Application Group Configuration == | == Application Group Configuration == | ||
* Increase Max # of Rows to reduce [[Table Segmentation in Content Manager OnDemand|Table Segmentation]] in the database | * Increase Max # of Rows to reduce [[Table Segmentation in Content Manager OnDemand|Table Segmentation]] in the database | ||
* Specify the CORRECT Expiration Type (Document, Load, Segment) | * Specify the CORRECT Expiration Type (Document, Load, Segment) | ||
* Use Indexes carefully | * Use Indexes carefully | ||
| Line 20: | Line 21: | ||
== Loading data into Content Manager OnDemand == | == Loading data into Content Manager OnDemand == | ||
* Load in large batches with small date ranges | * Load in large batches (hundreds to thousands of documents at a time) with small date ranges | ||
* Load chronologically | * Load chronologically to prevent breaking table segmentation in CMOD. | ||
* Use separate Load Servers | * Use separate Load Servers | ||