text: **13.3.3 Retrieval testing**
  
  The goal of retrieval testing is to verify that, under stressful system conditions, the maximum 
  number of concurrent users can be served while at the same time the system meets the 
  business requirements. The following process is a good general approach to retrieval testing 
  of the system: 
  
  (cid:2) Transaction type: Different types of transactions present different types of workloads on 
  
  the system. For example, logon, document query, and document retrieval all use different 
  components of the Content Manager OnDemand system. For each transaction type, 
  measure the throughput and response time for a number of concurrent users that exceed 
  the maximum predicted number. Tune and add resources to the system as needed until 
  the system exceeds the service level agreement (SLA) requirements. 
  
  (cid:2) Data types: The stored documents might be different sizes and data types (and might 
  
  invoke preview exits). Multiple document retrieval tests must be run to verify the 
  performance for the various types of stored documents. 
  
  (cid:2) User workloads: The users that access the system might all exhibit the same usage 
  
  patterns or might exhibit two or more usage patterns. The following process shows an 
  example usage pattern: 
  
  a. Log on. 
  b. Wait five seconds. 
  c. 
  d. Wait five seconds. 
  e. Retrieve a 10 KB document. 
  f. Wait 40 seconds. 
  g. Retrieve a 20 KB document. 
  h. Wait 60 seconds. 
  i. Log off. 
  
  Issue a document query with a maximum hit list size of 12 documents. 