Performance requirements for DS8000® HyperSwap with independent auxiliary storage pools (IASPs)
You should understand these performance considerations before configuring HyperSwap®.
Before you use HyperSwap, consider the following
requirements and guidelines:
- The source and target volumes in a HyperSwap Metro Mirror relationship must be the same storage type.
- The source and target logical volumes must be the same size.
- As with any synchronous replication technology, there are distance and bandwidth limitations that can affect performance.
- Similar to any system disk configuration, the number of disk units available to the application can have a significant affect on its performance. Putting more workload on a limited number of disk units may result in longer disk waits and ultimately longer response times to the application. This is important when it comes to temporary storage in a system configured with IASPs. All temporary storage is written to the SYSBAS disk pool. If your application does not use a lot of temporary storage, then you can get by with fewer disk arms in the SYSBAS disk pool. Remember, the operating system and basic functions occur in the SYSBAS disk pool.