MCP IOPS
A single HDD local hard drive was used for testing because the HDD itself could become the bottleneck. These tests focus on disk IOPS measurement and calculation, and certain real deployment scenarios require that a local drive not be used. Thus, the measurement for MCP IOPS is useful to calculate overall IO requirement. The three tables below offer three typical MCP IOPS configurations:
Table: MCP IOPS on physical server of single hex core, MP3 only
Ports | Physical MCP IOPS (kbps) | ||
---|---|---|---|
Total | Read | Write | |
60 | 21.88 | 14.93 | 6.95 |
120 | 43.25 | 29.64 | 13.60 |
180 | 63.28 | 43.37 | 19.91 |
200 | 71.47 | 49.35 | 22.12 |
210 | 74.95 | 51.58 | 23.37 |
220 | 78.40 | 53.93 | 24.47 |
230 | 82.51 | 56.83 | 25.68 |
240 | 85.28 | 58.37 | 26.90 |
Table: MCP IOPS on 6 VMs of dual hex core, MP3 only
MP3 only Ports |
Overall 6 VM MCP IOPS (kbps) | ||
---|---|---|---|
Total | Read | Write | |
120 | 43.672 | 29.679 | 13.993 |
240 | 87.477 | 59.280 | 28.197 |
300 | 109.292 | 73.848 | 35.445 |
360 | 130.965 | 88.917 | 42.047 |
420 | 151.706 | 103.095 | 48.611 |
480 | 171.290 | 116.053 | 55.237 |
540 | 194.772 | 132.867 | 61.905 |
600 | 215.101 | 146.882 | 68.219 |
660 | 236.654 | 161.990 | 74.664 |
720 | 259.100 | 177.279 | 81.820 |
Table: MCP IOPS on 6 VMs of dual hex core, MP3 + wav
MP3 + wav Ports |
Overall 6 VM MCP IOPS (kbps) | ||
---|---|---|---|
Total | Read | Write | |
120 | 173.607 | 146.092 | 27.515 |
240 | 348.369 | 292.884 | 55.486 |
300 | 434.511 | 364.898 | 69.613 |
360 | 522.447 | 439.412 | 83.035 |
420 | 600.880 | 504.682 | 96.198 |
480 | 693.861 | 583.965 | 109.896 |
540 | 780.187 | 656.958 | 123.229 |
600 | 859.359 | 722.907 | 136.453 |
660 | 790.737 | 664.024 | 126.713 |
The graph below compares the two tables MCP IOPS on physical server of single hex core, MP3 only and MCP IOPS on 6 VMs of dual hex core, MP3 only:
The graph below compares the two tables MCP IOPS on 6 VMs of dual hex core, MP3 only and MCP IOPS on 6 VMs of dual hex core, MP3 + wav:
The MCP IOPS is related to the test profile and ports, but on the same physical server and VMs.