vSTREAM-STL S2D Capabilities: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=== Test setup === | |||
Source: OPVXG Traffic Generator | Source: OPVXG Traffic Generator | ||
| Line 8: | Line 10: | ||
OptiView XG Traffic Generator version | OptiView XG Traffic Generator version | ||
vSphere: ESXi v6.7 with 300 IOS | |||
=== Traffic type === | |||
| | ||
| Line 16: | Line 20: | ||
| | ||
=== Traffic measured === | |||
=== Graphically with Link Monitor for 60' at 5' AVG: === | |||
| | ||
| Line 24: | Line 30: | ||
| | ||
=== Conclusion === | |||
Because the default capacity of a VSphere Standard Virtual Switch (VSS) is specified as 200kpps, we must conclude that vSTREAM-STL Stream to Disk performance is hardly affected by the number of CPU and memory assigned to the virtual machine. | |||
We did experience instability issues whenever the memory size was not in line with the numer of virtual CPU. You must provide 2GB of RAM per vCPU. This is also a recommendation of VMware itself. | |||
| | ||
[[Category:Private]] | [[Category:Private]] | ||
Revision as of 06:50, 5 August 2019
Test setup
Source: OPVXG Traffic Generator
Destination: ME: CRT-VIR-A-VVSTL62:if4
vSTREAM Standalone version 6.2.0-451 on NGS 6.2.0-658 with two MON interfaces (auto tsa 50/50)
OptiView XG Traffic Generator version
vSphere: ESXi v6.7 with 300 IOS
Traffic type
Traffic measured
Graphically with Link Monitor for 60' at 5' AVG:
Conclusion
Because the default capacity of a VSphere Standard Virtual Switch (VSS) is specified as 200kpps, we must conclude that vSTREAM-STL Stream to Disk performance is hardly affected by the number of CPU and memory assigned to the virtual machine.
We did experience instability issues whenever the memory size was not in line with the numer of virtual CPU. You must provide 2GB of RAM per vCPU. This is also a recommendation of VMware itself.