text: **3.10.1 The storage pool and Storwize V7000 cache relationship**
  
  The Storwize V7000 uses cache partitioning to limit the potential negative effects that a 
  poorly performing storage controller can have on the clustered system. The cache 
  partition allocation size is based on the number of configured storage pools. This design 
  protects against individual overloaded back-end storage system from filling system write 
  cache and degrading the performance of the other storage pools. For more information, 
  see Chapter 2, “System overview” on page 9. 
  
  Table 3-3 lists the limit of the write-cache data that can be used by a single storage pool. 
  
  Table 3-3 Limit of the cache data 
  
  <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>Number of storage pools</td><td>Upper limit</td></tr></thead><tbody><tr><td>1</td><td>100 %</td></tr><tr><td>2</td><td>66 %</td></tr><tr><td>3</td><td>40 %</td></tr><tr><td>4</td><td>30 %</td></tr><tr><td>5 or more</td><td>25 %</td></tr></tbody>
          </table> </body> </html>