302 IBM Content Manager OnDemand Guide
/SM590000Content Manager OnDemand tunable components
/SM590000Storage management tunable components: UNIX System Services, z/OS file system 
(zFS), hierarchical file system (HFS), OAM, Tivoli Storage Manager, and ASM
/SM590000Data components:
– Report file size, document file size (or in the case of large objects, report segment 
size), and number of documents per report.
– Number and distribution of triggers, fields, and indexes per document.
– Data type and required data conversion (if any).
– Resource collection for AFP and Portable Document Format (PDF).
– Document compressibility, which is a function of document data complexity and data 
type. Text (such as Line Data or SCS) is typically more compressible than AFP , which is 
typically more compressible than PDF .
– Storage object size (10 MB default): Contains 100 KB compressed object, which 
contains a compressed document.
– Exit routines/programs.
13.2.2  Recommendations
For the most optimal performance in loading, we recommend the following practices:
/SM590000For Multiplatforms and z/OS, run parallel load jobs to take advantage of multiprocessors, 
large memory pools, multiple data paths, and multiple disk drives. 
/SM590000Ensure that each parallel load is loading to a different application group.
/SM590000Ensure that you set up a different temp directory for each of the parallel loads. The -c 
indexDir indexer parameter (which specifies the directory in which the indexer stores 
temporary data) must always be specified for ARSLOAD and must be unique for each 
running ARSLOAD process.
/SM590000For IBM i, start multiple output queue monitors over a single output queue to improve 
throughput and take advantage of multiprocessors, large memory pools, and multiple disk 
drives.
/SM590000Each Content Manager OnDemand process is limited by the performance of a single 
processor. For example, the OS/400 indexer uses only one processor when it indexes a 
document. Using two or more processors in your system or LPAR does not improve the 
performance of the OS/400 indexer. However, by using two or more processors in your 
system or LPAR, you might be able to run multiple load jobs simultaneously. Y ou can start 
multiple output queue monitors over a single output queue to improve document load 
performance.
/SM590000For IBM i, the use of the Merge Spooled Files (MRGSPLFOND) command can provide 
significant performance improvements when you load SCS spooled files.