login vsi company logo login vsi company logo 250x40

 

Get the best possible VDI performance, density and availability with Login VSI
Our Solutions

Simulating VDI Users - Introduction to Login VSI Workloads

Simulating VDI Users - Introduction to Login VSI Workloads

Most people describe Login VSI as a “load generator”, but I don't feel this actually does it justice. The main differentiator between Login VSI and other load testing solutions is the fact that Login VSI generates load on a virtualized desktop environment by using virtual users to simulate the same behavior as your real users, instead of just static load. There's much more to consider when simulating those pesky and unpredictable humans. This enables any IT department to test the real-life impact of changes on the maximum capacity of their VDI environment without having to use (and bother) their real users.

To help you better understand how this actually works, I figured that it would make sense to write a blog post about the most important part of a Login VSI test, the virtual users, and the instructions they use to do their thing... the workload.

What is a workload?

For the most part a Login VSI Workload is a set of actions that are executed by the virtual user. These workloads perform operations intended to:

  • Determine a baseline performance level.
  • Execute a standard set of functions that allow for an objective performance measurement of the hosted desktop or application in order to determine VSImax.
  • Execute a custom set of functions that allow for the use of any Windows application to be used to measure performance and stress the system.

What are the components of a workload?

Login VSI workloads consist of a number of different functions.

1. Segments

The workloads included with Login VSI are each comprised of 5 segments. The first prepares the user environment and the other 4 run the applications and timers. Workloads can be created or modified to include fewer segments or more segments.

2. Preparation

Sets up the virtual user’s environment to eliminate unexpected or unwanted actions that may occur and cause the session to become stuck. This includes but is not limited to operations like setting file type associations, disabling popups, and setting security to allow for VSI applications access to the VSIshare.

3. Timers

The Login VSI Timer function uses native Windows applications and operations to determine system saturation and provides Login VSI with information necessary to evaluate the user experience. These operations are intended to stress and measure the host system’s resources like CPU, Memory and Storage. Without the Login VSI Timer function, there would be no VSImax or VSIbaseline measurements to determine the quality of the user experience. Timers are kicked off at a regular frequency and typically there will be a timer execution every 3 – 4 minutes. More detailed information about Timers, VSImax and VSIbase can be found in this blog post.

4. Application Actions

The application actions within the workload will use a number of functions to mimic human behavior of using the applications. These functions include but are not limited to the following: Open file, save file, close file, copy file, delete file, Print to PDF, Scroll, Compose and send an email, Watch videos, Edit Excel cells, Type fixed and random text.

5. Randomization

Humans are unpredictable and typically very random. Login VSI workloads do operations like typing random text as well as copying and opening random files to keep systems from caching repeated activities which could give a false sense of performance. Each workload is typically composed of multiple segments, each of which may use different applications in different orders. When testing with many users, the workloads will start with different segments in the workload and loop back around during the test. To simulate multiple, different types of users in the same test, it is possible to do what is called a ‘workload mashup’. For more information about workload mashup check out this blog post.

6. Idle Time

Unlike some benchmark software, humans don’t operate at a system’s CPU speed and they also take breaks. Wait times and idle times are also built into workloads to simulate a human’s natural click and typing speed as well as built-in bathroom and coffee breaks.

simulating login vsi workloads 30 sessions

30 user sessions simulated by Login VSI

Baseline

While the baseline is not necessarily a predetermined workload component, it is a phase in the test that is important in determining user experience and the calculation of VSImax. As the Login VSI workload starts up, measurements are taken on the system in an optimal state, prior to becoming saturated with a large volume of user activity. This baseline is used to calculate the best user experience as well as the threshold for VSImax—the point at which the system becomes so saturated it no longer provides a good end user experience.

What applications are used in default workloads?

Login VSI offers by default four flavors of workloads without any need for scripting:

  1. Task Worker: Microsoft Word, Microsoft Outlook, Internet Explorer, Adobe Reader, Microsoft Excel
  2. Office Worker: Microsoft Word, Microsoft Outlook, Internet Explorer, Adobe Reader, Microsoft PowerPoint, Microsoft Excel, Photo Viewer
  3. Knowledge: Microsoft Word, Microsoft Outlook, Internet Explorer, Adobe Reader, Microsoft PowerPoint, Microsoft Excel, Freemind / Java, Photo Viewer
  4. Power Worker: Microsoft Word, Microsoft Outlook, Internet Explorer, Adobe Reader, Microsoft PowerPoint, Microsoft Excel, Freemind / Java, Photo Viewer, Simulated application install.

NOTE: For many of the applications in power worker, larger files and higher resolution media will be used. 

login vsi workloads task office knowledge power

Login VSI offers by default four flavors of workloads

What makes the workloads different?

While many of the applications listed above are the same between workloads, each one, from Task Worker to Power Worker becomes increasingly aggressive while continuing to maintain the behavior of the type of user the workload is named after. One of the things that makes the workloads different in terms of their aggressiveness is how many of the applications are run concurrently, or within the workload segment (see above).  
In our labs at Login VSI, we have run each of the default workloads against a specified hardware environment, virtual machine configuration and set of users. During this test we observed differences in the impact to the system and behavior of the workload. Below you will find a table that helps to identify the behaviors of the different workloads.

NOTE: These values will be different depending on the hardware used, virtual machine optimizations and user concurrency. The information provided below is only provided to help you understand how they behave relative to each other.

Workload NameLogin VSI VersionApplications OpenedEstimated CPU UsageEstimated IOPS per userTypical VM Memory ProfileTypical VM vCPU Profile
Task Worker 4.1+ 2-7 70% 6.0 1.0 GB 1vCPU
Office worker 4.1+ 5-8 82% 8.1 1.5 GB 1vCPU
Knowledge 4.1+ 5-9 100% 8.5 1.5 GB 2vCPU
Power worker 4.1+ 8-12 119% 10.8 2.0 GB 2vCPU+

Other types of workloads

Login VSI workloads can be customized to add any line-of-business applications our customers wish to have the virtual users operate. My colleague Mark recently wrote a great blog with 5 best practices for workload customization. In addition, Login VSI also offers a storage workload designed to stress the storage subsystem as well as a graphics framework that is designed to stress the graphics resources like CPU and GPU.

For more information

 


 

Start using Login VSI today

Our industry-standard software is built to help you avoid problems, lower costs and improve performance. Request a Quote or get your free Trial below, and benefit from our award-winning services.

Free Price Request  Your Free Trial

 


About the company Login VSI

The company Login VSI provides end-user performance insights for virtualized desktop and server-based computing environments. Enterprise IT departments use flagship product Login VSI (for load testing) and Login PI (for continuity testing) in all phases of their virtual desktop deployment—from planning to deployment to change management—to build and safeguard a good performance, a high availability, and (as a result) a good and consistent end-user experience. For more information about Login VSI or for a free test license contact us.

About the author

Blair Parkhill (@SANspyder) joined Login VSI in the summer of 2015 as the director of products. Blair has been a marketing leader, avid architect and supporter of customer-focused technology solutions and technical marketing since the late 1990s. Residing in Colorado Springs, he spends much of his time playing music, doing yoga, hiking in the mountains and geeking out with the latest tech.


Tags: Login VSI, Load Testing, Workloads, VSImax, Support

Popular Blogs

Login VSI Blog - Ongoing Effects CPU Flaws

The Ongoing Effects of Intel CPU Flaws

The Ongoing Effects of Intel CPU Flaws Over the last year, we’ve seen many Intel CPU hardware flaws come to light and when news first broke about Meltdown & Spectre there was a lot of panic: "should we patch?", "What’s the performance impact?", "Can we still rely on this hardware?" Continue Reading
Login VSI Blog - How-To Update, Protect Against RIDL, Fallout MDS Vulnerability

How-To: Update, Protect Against RIDL, Fallout MDS Vulnerability

RIDL & Fallout MDS vulnerabilities, impact on VDI performance & actions to take. FAQs we’re receiving & updates on performance tests executed to patch flaws Intel calls “Microarchitectural Data Sampling (M.D.S.)” aka: Rogue In-Flight Data Load (RIDL), Fallout, ZombieLoad & Store-to-Leak Forwarding. Continue Reading
Login VSI Blog - Teaser Image - A Practical Guide to VDI Change Management - Part 1

A Practical Guide to VDI Change Management

Part 1: IT Change Management in general The first in an 8-part series, this practical guide to VDI Change Management will guide you through the transformation of the IT department from a back-end function into a core competency for every modern organization. Continue Reading
Login VSI - Blog - Login PI Blog Teaser Image - Windows Virtual Desktop: How To Monitor User Experience With Login PI

Windows Virtual Desktop – How to Monitor User Experience?

Microsoft has just announced the public preview of their new Windows Virtual Desktop (WVD) offering at Microsoft Ignite on Tour in Amsterdam today. For those of you who’ve not followed the rumors or the private beta, here’s the outline... Continue Reading
A Practical Guide To VDI Change Management, Part 3

A Practical Guide to VDI Change Management

Part 3: Change Accelerates with Windows 10 The third in an 8-part series, this practical guide to VDI Change Management gives you the low-down on the what, why and how of Windows 10 updates and changes Continue Reading
Login VSI Blog - Teaser Image - A Practical Guide to VDI Change Management - Part 2

A Practical Guide to VDI Change Management

Part 2: Why VDI is very sensitive to change The second in an 8-part series, this practical guide to VDI Change Management highlights the importance of effective Change Management. With all the complexities of VDI environments, any failure can severely impact your business. Continue Reading
Cookie Settings