text: **13.2.2 Recommendations**
  
  For the most optimal performance in loading, we recommend the following practices: 
  
  (cid:2) For Multiplatforms and z/OS, run parallel load jobs to take advantage of multiprocessors, 
  large memory pools, multiple data paths, and multiple disk drives. 
  
  (cid:2) Ensure that each parallel load is loading to a different application group. 
  
  (cid:2) Ensure 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. 
  
  (cid:2) For 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. 
  
  (cid:2) Each 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. You can start 
  multiple output queue monitors over a single output queue to improve document load 
  performance. 