Difference between revisions of "Login VSI Workloads"

From Login VSI Documentation
Jump to: navigation, search
(Power Worker)
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
This section descibes the default workloads that come with the Login VSI product. These new and improved workloads also feature a new timer mechanism, which is executed multiple times within each workload, and determines the performance of the system during testing. The different timers are easy to identify, as the look like this: VSI_Timer41.
+
This section describes the default workloads that come with the Login VSI product. These new and improved workloads feature a new timer mechanism, which is executed multiple times within each workload, and determines the performance of the system during testing.
  
 
'''Recommended:''' [https://www.loginvsi.com/blog/login-vsi/665-simulating-vdi-users-introduction-to-login-vsi-workloads Simulating VDI Users - Introduction to Login VSI Workloads]
 
'''Recommended:''' [https://www.loginvsi.com/blog/login-vsi/665-simulating-vdi-users-introduction-to-login-vsi-workloads Simulating VDI Users - Introduction to Login VSI Workloads]
 +
 +
'''Note''': For more information on the additional workloads that are available to download, please see the [https://www.loginvsi.com/documentation/index.php?title=Login_VSI_Workload_Add-ons Workload Add-ons] section.
  
 
==Task Worker==
 
==Task Worker==
This is a light workload, which runs fewer application and starts/stops them less frequently than the other workloads, resulting in lower CPU, memory and IO usage.  
+
This is a light workload, which runs fewer application and starts/stops them less frequently than the other workloads, resulting in lower CPU, RAM and IO usage.  
  
 
The Task Worker workload uses the following applications:
 
The Task Worker workload uses the following applications:
Line 14: Line 16:
 
*MS Word
 
*MS Word
  
It also uses native Windows Apps, such as Notepad and 7-Zip to complete the print and zip actions used by the workload meta functions.
+
It also uses native Windows apps (Notepad and 7-Zip) to complete the print and zip actions used by the workload meta functions.
  
 
==Office Worker==
 
==Office Worker==
The main goal of this workload is to be deployed in environments that only use 1(v)CPU in their VMs. It is based on the Knowledge Worker workload, but has less less resource usage in comparison.
+
The main goal of this workload is to be deployed in environments that only use 1(v)CPU. It is based on the Knowledge Worker workload, but has less resource usage in comparison. However, it is more intensive than the Task Worker workload.
  
 
The Office Worker workload uses the following applications:
 
The Office Worker workload uses the following applications:
Line 29: Line 31:
 
*Photo Viewer  
 
*Photo Viewer  
  
It also uses native Windows Apps, such as Notepad and 7-Zip to complete the print and zip actions used by the workload meta functions.
+
It also uses native Windows apps (Notepad and 7-Zip) to complete the print and zip actions used by the workload meta functions.
  
 
==Knowledge Worker==
 
==Knowledge Worker==
The Knowledge Worker is designed for 2vCPU environments. This workload provides stable and reliable VSImax numbers via a well-balanced medium workload that stresses the system smoothly, resulting in higher CPU, memory and IO usage.
+
The Knowledge Worker is designed for 2(v)CPU environments. This is a well-balanced intensive workload that stresses the system smoothly, resulting in higher CPU, RAM and IO usage.
  
 
The Knowledge Worker workload uses the following applications:
 
The Knowledge Worker workload uses the following applications:
Line 45: Line 47:
 
*Photo Viewer  
 
*Photo Viewer  
  
It also uses native Windows Apps, such as Notepad and 7-Zip to complete the print and zip actions used by the workload meta functions.
+
It also uses native Windows apps (Notepad and 7-Zip) to complete the print and zip actions used by the workload meta functions.
  
 
==Power Worker==
 
==Power Worker==
The Power Worker is designed for 2(v)CPU+ environments. This is a very intensive workload that puts maximum stress on the system, resulting in very high CPU, memory and IO usage.  
+
The Power Worker is designed for 2(v)CPU+ environments. This is a very intensive workload that puts maximum stress on the system, resulting in very high CPU, RAM and IO usage.
 +
 
 +
'''Important''': You must install the [https://www.loginvsi.com/documentation/index.php?title=Login_VSI_Pro_Library Pro Library] to be able to use this workload.
  
 
The Power Worker workload uses the following applications:
 
The Power Worker workload uses the following applications:
Line 62: Line 66:
 
*Simulated application install
 
*Simulated application install
  
For many of the applications in this workload, larger files and higher resolution media will be used. It also uses native Windows Apps, such as Notepad and 7-Zip to complete the print and zip actions used by the workload meta functions.
+
For many of the applications in this workload, larger files and higher resolution media are used. It also uses native Windows apps (Notepad and 7-Zip) to complete the print and zip actions used by the workload meta functions.
  
 
==Workload Resource Usage==
 
==Workload Resource Usage==
Line 122: Line 126:
 
101%
 
101%
 
|
 
|
8,1
+
8.1
 
|
 
|
1,5GB
+
1.5GB
 
|
 
|
 
1(v)CPU
 
1(v)CPU

Latest revision as of 11:40, 7 November 2017

This section describes the default workloads that come with the Login VSI product. These new and improved workloads feature a new timer mechanism, which is executed multiple times within each workload, and determines the performance of the system during testing.

Recommended: Simulating VDI Users - Introduction to Login VSI Workloads

Note: For more information on the additional workloads that are available to download, please see the Workload Add-ons section.

Task Worker

This is a light workload, which runs fewer application and starts/stops them less frequently than the other workloads, resulting in lower CPU, RAM and IO usage.

The Task Worker workload uses the following applications:

  • Adobe Reader
  • Internet Explorer
  • MS Excel
  • MS Outlook
  • MS Word

It also uses native Windows apps (Notepad and 7-Zip) to complete the print and zip actions used by the workload meta functions.

Office Worker

The main goal of this workload is to be deployed in environments that only use 1(v)CPU. It is based on the Knowledge Worker workload, but has less resource usage in comparison. However, it is more intensive than the Task Worker workload.

The Office Worker workload uses the following applications:

  • Adobe Reader
  • Internet Explorer
  • MS Excel
  • MS Outlook
  • MS PowerPoint
  • MS Word
  • Photo Viewer

It also uses native Windows apps (Notepad and 7-Zip) to complete the print and zip actions used by the workload meta functions.

Knowledge Worker

The Knowledge Worker is designed for 2(v)CPU environments. This is a well-balanced intensive workload that stresses the system smoothly, resulting in higher CPU, RAM and IO usage.

The Knowledge Worker workload uses the following applications:

  • Adobe Reader
  • Freemind/Java
  • Internet Explorer
  • MS Excel
  • MS Outlook
  • MS PowerPoint
  • MS Word
  • Photo Viewer

It also uses native Windows apps (Notepad and 7-Zip) to complete the print and zip actions used by the workload meta functions.

Power Worker

The Power Worker is designed for 2(v)CPU+ environments. This is a very intensive workload that puts maximum stress on the system, resulting in very high CPU, RAM and IO usage.

Important: You must install the Pro Library to be able to use this workload.

The Power Worker workload uses the following applications:

  • Adobe Reader
  • Freemind/Java
  • Internet Explorer
  • MS Excel
  • MS Outlook
  • MS PowerPoint
  • MS Word
  • Photo Viewer
  • Simulated application install

For many of the applications in this workload, larger files and higher resolution media are used. It also uses native Windows apps (Notepad and 7-Zip) to complete the print and zip actions used by the workload meta functions.

Workload Resource Usage

We have created a table that contains the resource usage per workload, which provides crucial information for advanced users. These metrics are measured from a single user / VM, with all metrics based on the Knowledge Worker workload.

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 one another.

Workload Name

VSI Version

Apps Open

CPU Usage

Disk Reads

Disk Writes

IOPS

RAM

(v)CPU

Task Worker

4.1.x

2-7

70%

79%

77%

6

1GB

1(v)CPU

Office Worker

4.1.x

5-8

82%

90%

101%

8.1

1.5GB

1(v)CPU

Knowledge Worker

4.1.x

5-9

100%

100%

100%

8.5

1.5GB

2(v)CPU

Power Worker

4.1.x

8-12

119%

133%

123%

10.8

2GB

2(v)CPU+