1. IBM Storwize V7000.
part II
Introduction
I had already tested the IBM Storwize V7000, but in a configuration that is far from the maximum.
In synthetic test of SPC-1, IBM for Storwize V7000 was able to demonstrate the result in 53K iops with
average response time of 11 ms (you can remember these two numbers - later they will be compared with anything
else). It took evenly distribute the load on 240xHDD SFF 10K, gathered in the raid group R10.
Is it possible to achieve similar results to real-world business applications? (without using SSD)
2. The load is in a production environment.
So, what we have - IBM Storwize V7000 (1 +9 enclosures), where data is distributed across three disk pools
(Raid group - both R10 and R6), total used 208hHDD SFF 10K (that is slightly less than the used IBM in the above
SPC-1 test). Load which is shown below*, not the result of a synthetic test - is the load on the database for real
business applications (mix OLTP/OLAP).
* load profile is different from the SPC-1
Disk total KB/s
Disk Read KB/s Disk Write KB/s IO/sec
1200 100000
Thousands
90000
1000 80000
800 70000
60000
KB/sec
IO/sec
600 50000
40000
400 30000
200 20000
10000
0 0
08:45
09:25
16:25
09:05
09:45
10:05
10:25
10:45
11:05
11:25
11:45
12:05
12:25
12:45
13:05
13:25
13:45
14:05
14:25
14:45
15:05
15:25
15:45
16:05
16:45
17:05
17:25
17:45
18:05
18:25
18:45
Disk Service Time msec/xfer
hdisk6 hdisk5 hdisk4 hdisk7 hdisk8 hdisk1 hdisk2 hdisk3
hdisk21 hdisk20 hdisk18 hdisk0 hdisk19 hdisk9 hdisk10
10
8
6
4
2
0
09:25
14:45
18:25
08:45
09:05
09:45
10:05
10:25
10:45
11:05
11:25
11:45
12:05
12:25
12:45
13:05
13:25
13:45
14:05
14:25
15:05
15:25
15:45
16:05
16:25
16:45
17:05
17:25
17:45
18:05
18:45
As seen in the charts above, managed to get ~ 90 000 iops with an average response time of ~ 5ms. Which I
think is quite a good result. But wait, there's only one of dozens of hosts, the data of which are located at this IBM
Storwize V7000. The rest of the server will not create such a significant load on the storage system, but still. Below
presents the total utilization storage discussed.
3. The recorded peak load ~ 106,000 iops, where:
- Used only thin-provisioned volumes
- Were active 12x FlashCopy mapping (snapshots)
The load on the CPU in this case was, as expected, it is significant.
