Difference between revisions of "Login VSI Workloads"

From Login VSI Documentation
Jump to: navigation, search
(Office Worker)
Line 25: Line 25:
  
 
==Office Worker==
 
==Office Worker==
There is a new workload added that has no precursor, called the Office worker. This workload is based on the Knowledge worker workload. The main goal of the Office worker workload is to be deployed in environments that use only 1vCPU in their VM’s. We have included the following applications into the Office worker workload:
+
This workload has no precursor, but is based on the Knowledge Worker. The main goal of this workload is to be deployed in environments that only use 1(v)CPU in their VMs. We have included the following applications into the Office worker workload:
  
*Outlook
+
*Adobe Reader
*Microsoft Internet explorer
 
*Microsoft word
 
*Adobe reader
 
*Micrsoft Powerpoint
 
*Microsoft Excel
 
*Login VSI photo viewer
 
 
*Doro PDF Writer
 
*Doro PDF Writer
 +
*Internet Explorer
 +
*MS Excel
 +
*MS Outlook
 +
*MS PowerPoint
 +
*MS Word
 +
*Photo Viewer
  
 
Overall the Officeworker workload has less resource usage in comparison to the Knowledgeworker workload. The difference was calculated in the same environment with VM’s that had 2vCPU’s.
 
Overall the Officeworker workload has less resource usage in comparison to the Knowledgeworker workload. The difference was calculated in the same environment with VM’s that had 2vCPU’s.

Revision as of 16:15, 2 November 2017

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.

Recommended: Simulating VDI Users - Introduction to Login VSI Workloads

Task Worker

This workload is more diverse than its predecessor, which focused mostly around Excel and Internet Explorer actions.

The Task Worker workload uses the following applications:

  • 7-Zip
  • Adobe Reader
  • Internet Explorer
  • Microsoft Excel
  • Microsoft Outlook
  • Microsoft Word
  • Notepad

The actual resource usage of the workload has also changed:

  • There is a Disk Write increase of approximately 18%
  • There is a Disk Read increase of approximately 52%
  • There is an IOPS increase of approximately 15%
  • There is a CPU usage increase of approximately 6%

Office Worker

This workload has no precursor, but is based on the Knowledge Worker. The main goal of this workload is to be deployed in environments that only use 1(v)CPU in their VMs. We have included the following applications into the Office worker workload:

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

Overall the Officeworker workload has less resource usage in comparison to the Knowledgeworker workload. The difference was calculated in the same environment with VM’s that had 2vCPU’s.

  • There is no change in Disk Write
  • There is Disk Read decrease of approximately 11%
  • There is an IOPS decrease of approximately 13%
  • There is a CPU usage decrease of approximately 22%

Knowledge Worker

Both the Medium and the Knowledge worker workloads have been designed as 2vCPU workloads. The Knowledge worker has been totally redesigned to support creating a 1vCPU workload called the office worker. The goal of the new Knowledge worker workload was to result in more stable and reliable VSImax numbers that are the same or very close to tests executed with Login VSI 4.0 Medium. The changes are:

  • Removed flash games
  • Over all balancing of the workload
  • Added copy and zip actions

The goal of the new Knowledge worker workload was to be more stable, more smooth and still generate the same amount of VSImax as the Medium. There are not, like the Light workload, applications added to increase or decrease the load.The actual resource usage of the workload has also changed (compared from Medium to Knowledge worker):

  • There is a Disk Write increase of approximately 7%
  • There is a Disk Read increase of approximately 3%
  • There is an IOPS increase of approximately 13%
  • There is a CPU usage increase of approximately 1%

Power Worker

The Power worker is the new Heavy workload. In some scenario’s we discovered that the Heavy workload was not as heavy as we had designed. At some points (Storage) it was even less intensive as the Medium workload. This was not the desired result for a Heavy workload. The workload itself did not change in applications only in resources used. The changes are:

  • Added copy and zip actions
  • Balanced the CPU usage
  • Increased the amount of Disk Reads
  • Increased the amount of Disk Writes

The actual resource usage of the workload has been changed (compared from Heavy to Power worker)

  • There is a Disk Write increase of approximately 30%
  • There is a Disk Read increase of approximately 49%
  • There is an IOPS increase of approximately 54%
  • There is a CPU usage decrease of approximately 4%

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

Memory

vCPU

Task Worker

4.1.x

2-7

70%

79%

77%

6

1GB

1vCPU

Office Worker

4.1.x

5-8

82%

90%

101%

8,1

1,5GB

1vCPU

Knowledge Worker

4.1.x

5-9

100%

100%

100%

8.5

1.5GB

2vCPU

Power Worker

4.1.x

8-12

119%

133%

123%

10.8

2GB

2vCPU+