text: **13.3.4 System testing**
  
  After the load and retrieval tests are performed individually, it is important to perform an 
  overall system test. This test must include running*everything*in parallel up to the maximum 
  expected system usage. Everything includes load, retrieval, expiration, migration, duplication, 
  and backup operations. The goal is to ensure that under the most stressful conditions 
  possible, the system meets business requirements. 
  
  **Note:**
  
  <html>
          <head> <meta charset="UTF-8">
          <style>
          table, th, td {
              border: 1px solid black;
              font-size: 10px;
          }
          </style> </head>
          <body>
          <table frame="hsides" rules="groups" width="100%%">
              [html]<thead><tr><td>•</td><td>The performance tuning process demands great skill, knowledge, and experience, and it cannot be performed by only analyzing statistics, graphs, and figures.</td></tr></thead><tbody><tr><td>•</td><td>The goal is to ture the Content Manager OnDemand server. You can “ see ” the bottleneoks in the server only if both the client and the network are clear of bottlenecks.</td></tr><tr></tr></tbody>
          </table> </body> </html>