7.6 I/O throttling You can limit the number of I/O operations that a volume realizes. This limitation is called I/O  throttling or governing. The limit can be set in terms of number of I/O operations per second  (IOPS) or bandwidth (MBps, GBps, or TBps). By default, I/O throttling is disabled, but each  volume can have up to two throttles defined: one for bandwidth and one for IOPS. When you choose between IOPS or bandwidth for I/O throttling, consider the disk access  profile of the application that is the primary volume user. Consider these scenarios: GLYPH<SM590000> Large amounts of I/O:  Database applications generally issue large amounts of I/O  operations, but transfer a relatively small amount of data. In this case, setting an I/O  governing throttle that is based on bandwidth might not achieve much. A throttle based on  IOPS is better suited to this use case. GLYPH<SM590000> Large amounts of data:  Conversely, a video streaming application generally issues a  small amount of I/O, but transfers large amounts of data. Therefore, in this case it is better  to use a bandwidth throttle for the volume. GLYPH<SM590000> I/O governing does not affect FlashCopy and data migration I/O rates. GLYPH<SM590000> I/O governing on Metro Mirror or Global Mirror secondary volumes does not affect the  rate of data copy from the primary volume. An I/O governing rate of  0  does not mean that zero IOPS or bandwidth can be achieved for  this volume, but rather that no throttle is set for this volume. Note: 298  Implementing the IBM System Storage SAN Volume Controller with IBM Spectrum Virtualize V8.2.1