Test the capacity of your VDI storage solution with the Login VSI Storage Workload
In November we were excited to offer vendors of storage solutions a new add-on to Login VSI that is designed specifically to test storage capacity. Very quickly, vendors like VMware, HP, SanDisk, Cisco, Nutanix, Overland Storage and Tegile have embraced the new workload and now include the higher level IOPs into their daily testing operations. This signals quick acceptance of a strong new workload specifically designed for storage vendors.
Why did we build the storage workload?
The Login VSI Storage Workload is designed to help vendors and enterprise organizations perform large-scale storage capacity tests. It is used to validate VDI storage requirements with a smaller footprint on infrastructure required for the test whilst still producing valid results with a significant higher IOPs level.
How does the Login VSI Storage Workload work?
We started working with the idea that everything should be as realistic as possible, therefore it works with real everything: real IOPs, real data, real applications, real infrastructure and minimal synthetic disk IO load. It has a significantly higher IOPs (depends on OS and AV tuning) than the Office Worker with a similar CPU and Memory profile (at least 2x in a regular VSI test with logons included and at least 3x in a steady state test without active logons).
The Storage Workload runs in Direct Desktop Mode, therefore there is no need for a launcher infrastructure with a launcher for every 25 to 50 users. Note that the Login VSI Storage Workload is not compatible with Server Based Computing, Terminal Server or XenApp scenarios.
In short: if the Storage Workload runs smoothly, you are sure your storage infrastructure can handle the IOPs, because the Storage Workload is specially designed to perform large-scale storage capacity tests.
This graph displays the difference in Reads/Writes between the Storage Workload and the Office Worker workload
What sets the Storage Workload apart from regular workloads in Login VSI?
The Login VSI Storage Workload is best used in conjunction with Login VSI. The storage workload proves the capacity of storage solutions only. To test the performance and capabilities of the overall system and overall use cases, please use the regular Login VSI workloads as well.
The Knowledge Worker workload in Login VSI was radically modified to suit storage testing in the following ways:
- CPU-only intensive operations are removed in favor of IO-intensive operations
- Browse and Edit sections are removed or minimized, as they have no specific impact on disk IO
- The Login VSI Storage Workload loops every 16 minutes instead of the 48 minutes typical for the Knowledge Worker profile
- At the end of each loop, after all apps are closed, the VSImemoryeater.exe consumes maximum memory for a couple of seconds (105% of available memory). This will clear any applications that are still cached in Windows memory. The next time these apps are started in a new loop, it will generate the same read IO as if the application is started for the first time
The VSImax, Login VSI’s easy-to-understand measure point of how many users can run in the environment before the performance reaches an unacceptable level, is less relevant when it comes to storage tests. In fact, you do not want to reach the VSImax at all with storage tests. Not reaching your VSImax indicates that the amount of users you tested with can be run on your platform.
We believe that the Login VSI Storage Workload is beneficial to all vendors of storage solutions to test their storage platform. If your tests with the Storage Workload run successfully, you can be sure that your storage offering can meet the severe storage needs of the specific VDI environment.