Cover. WinCC/Server Virtualization. WinCC. Technical Information April Applications & Tools. Answers for Industry.

Transcription

1 Cover / Virtualization Technical Information April 2011 Applications & Tools Answers for Industry.

2 Industry Automation and Drive Technologies Service & Support Portal This article is taken from the Service Portal of Siemens AG, Industry Automation and Drive Technologies. The following link takes you directly to the download page of this document. If you have any questions about this document, please contact us at the following address: 2 / Virtualization V1.0, Entry ID:

3 s Automation Task 1 Automation Solution 2 Procedure for the Virtualization 3 SIMATIC / Virtualization Framework Conditions for the Measurements 4 Test Scenarios and Basic Performance Data 5 Diagnostic Capabilities 6 Glossary 7 Links & Literature 8 History 9 / Virtualization V1.0, Entry ID:

4 Warranty and Liability Warranty and Liability Note The application examples are not binding and do not claim to be complete regarding configuration, equipment and any eventuality. The application examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These application examples do not relieve you of the responsibility to use sound practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these application examples at any time without prior notice. If there are any deviations between the recommendations provided in this application example and other Siemens publications e.g. Catalogs the contents of the other documents have priority. We accept no liability for information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act ( Produkthaftungsgesetz ), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract ( wesentliche Vertragspflichten ). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health. The above provisions do not imply a change in the burden of proof to your detriment. It is not permissible to transfer or copy these Application Examples or excerpts thereof without express authorization from Siemens Industry Sector. 4 / Virtualization V1.0, Entry ID:

5 Preface Preface Objective of this application This document provides an overview over the / Virtualization. Typical configurations on virtualized servers are displayed and measured performance data is represented. Core topics of this application The following main points are discussed in this application: Display of typical configurations Display of performance data in the various configurations Monitoring the performance of all guest systems Validity This document is valid for / V7.0 SP virtualization_en.doc / Virtualization V1.0, Entry ID:

6 Table of Contents Table of Contents Warranty and Liability... 4 Preface Automation Task Overview Virtualization requirements Automation Solution What is virtualization? Definition Advantages of the virtualization Requirements Required software ESX server with guest systems systems Further information Procedure for the Virtualization Process and required software Procedure in detail Framework Conditions for the Measurements Hardware used Configuration of the guest systems Used software Test Scenarios and Basic Performance Data standalone and one and two Standard s and three Standard s on ESXi (1) and four s on ESXi (2) on ESXi (1) and four Standard s on ESXi (2) on ESXi (1) and four Multi s on ESXi (2) and four Standard s and four Multi s on one ESXi on ESXi (1) and five Standard s on ESXi (2) on ESXi (1) and five Standard s on ESXi (2) and six Standard s on one ESXi and six Multi s on one ESXi Using redundant server on one or two ESXi servers Effects of the redundancy switch-over on the CPU load Two redundant servers as stand-alone stations on an ESXi server Two redundant server without operation as stand-alone stations on ESXi (1) with four Multi s on ESXi (2) Two ESXi servers with one redundant server each and two clients Two redundant servers without operation with six multi clients on one ESXi server Two ESXi servers with one redundant server each and three clients each / Virtualization V1.0, Entry ID:

7 Table of Contents Two redundant servers on ESXi (1) and one client with /Webnavigator, as well as 3 Webs on ESXi (2) Two redundant servers and one client with /Webnavigator, as well as 3 Webs on one ESXi Using one (external) engineering station for downloading the projects85 6 Diagnostic Capabilities Diagnosis with VMware vsphere Diagnosis in the virtual system Glossary Links & Literature Literature Internet links History / Virtualization V1.0, Entry ID:

8 1 Automation Task 1.1 Overview 1 Automation Task 1.1 Overview Introduction Virtualization of servers are already of high importance in information technology. In automation technology the advantages of virtualization shall also be reached. Description of the automation task Typical configurations of systems shall be virtualized. Which infrastructure and which configuration steps are necessary in order to virtualize plants? 1.2 Virtualization requirements The requirements for virtualized computers are identical to those for real computers. During runtime no difference to real computers shall be noticeable. 8 / Virtualization V1.0, Entry ID:

9 2 Automation Solution 2.1 What is virtualization? 2 Automation Solution 2.1 What is virtualization? Definition Virtualization Virtualization refers to the runnable mapping of one or several computers on a real computer. On a real computer a special software runs which provides one or several virtual computers parallel. The virtual computers can be started and stopped independent of each other. Even after a crash only the respective virtual computer is affected. Layout for virtualization Figure 2-1 Virtualized System 1 Virtualized System n Memory CPUs Network card Hard disks Graphics card Network card Sound card CPUs Memory Sound card Graphics card Hard disks Network card CPUs Memory Hard disks Graphics card Sound card Physical Hardware Physical PC A physical PC provides its hardware to several virtualized systems. / Virtualization V1.0, Entry ID:

10 Application Application for for virtualization virtualization 2 Automation Solution 2.1 What is virtualization? Differences between server-based and client-based virtualization Figure 2-2 -based Virtualization -based Virtualization (z.b. Application (z.b. VMware VMware Workstation) for virtualization (e.g. VMware Workstation) Workstation) Virtualized system Virtualized Virtualisiertes System Virtualisiertes Virtualisiertes System 1 System 2 System 3 n Application Application 1 n (e.g. MS (e.g. Word) MS Word) App. n App. (e.g.word) 1 (e.g.word) Operating system (e.g. Windows) Virtualized Hardware App. 1App. n (e.g.word) (e.g.word) Operating system (e.g. Windows) Virtualized Hardware Operating System (e.g. Windows) Application for Virtualization (=operating system) Hardware Hardware Physical PC Physical PC Operation directly at the PC via graphics card and monitor. No direct operation. Operation e.g. via one or several RDP clients. RDP 10 / Virtualization V1.0, Entry ID:

11 2 Automation Solution 2.1 What is virtualization? Advantages of the virtualization Reduction of the hardware costs Reduced HW costs through consolidating several physical computers. (The cost reduction results from a better hardware utilization.) On the client side more cost-efficient hardware is possible. Expanded application areas: SIMATIC Thin solutions (PC, Panel, mobile PDA). Reducing the time expenses for service and maintenance Shorter times for updates and backups since these are executed from a central place Reduced maintenance cost and time through central administration. configuration by means of remote management tools. Increased safety Increased safety through remote access and centralized rights management. Virtually no possible attacks for Thin s, central protection at the virtual server. Increased availability Exchange of hardware at the virtual server is possible during runtime. 1 Increased flexibility Additional clients can be added on demand simply by starting a further VMware session. Additional clients for special tasks can simply run in the background: RDP 2 /VNC 3 -solutions for remote or mobile accesses Provision of substitute computers as virtual systems, e.g. during maintenance of a system a substitute system can be used instead. 1 When using the respective virtualization hardware. 2 Windows Remote Desktop protocol: There is a number of possible clients for various operating systems of for mobile devices. (The server is located in the Windows operating system.) 3 Virtual Network Computing: alternative option for remote control of operating systems. (A server is required on the operating system. Viewing requires a client, which are also available for various operating systems or for mobile devices. / Virtualization V1.0, Entry ID:

12 2 Automation Solution 2.2 Requirements 2.2 Requirements Note WPF controls in VMware offers using WPF controls for the visualization. This option does not work on virtualized systems! (See Literature \4\.) Required software Virtualization software VMware Player and VMware Converter or VMware Workstation VMware vsphere SIMATIC Software and operating system (version depending on the application) Windows operating system (depending on the application) Windows 2003 or Windows 2008 or ESX server with guest systems ATTENTION The application/administration is required to supply and ensure sufficient system resources on the virtualization server and the virtual systems. Table 2-1 Features Requirements Number of CPU cores For the ESX server at least two real CPU cores are required. Separation of networks Terminal bus and plant network must be separated with separate real network cards. Graphics card settings 32MB VMware Tools VMWare tools must be installed on the guest computers. CPU load The CPU load system must not exceed a load of >75%. (source: according to VMWare) RAM For secure operation a work memory of 2 GB must be reserved for the ESXi server. (For communication/network activities and management of the ESXi.) 12 / Virtualization V1.0, Entry ID:

13 2 Automation Solution 2.2 Requirements systems Table 2-2 Features Requirements ATTENTION Number of CPU cores Modules Separation of networks CPU load VMware tools Hard disk storage management Operating states server: a guest system requires at least two logic CPU cores. : a guest system requires at least one logic CPU core. At least 2 physical modules are required. (one of which exclusively for the PLC bus) Separation of terminal, PLC and Windows networks. If necessary, the terminal and Windows network can be combined. The CPU load of the assigned logic CPU cores must not exceed 70% to 80%. Note When archiving large data volumes a respective reserve is required (high I/O load). (This load is given at a capacity of 70%-80%.) VMWare tools must be installed on the guest computers. (This yields a better performance.) If you are not using a dynamic storage management (the size of the hard disk file adjusts dynamically to the used capacity.). Pausing of the guest systems, as well as VMWare options (vmotion) are not supported. The guest systems must be treated like real /s. Please note the standard requirements for installations. These are available in the release note on or under the following link &TopicId= Note Chapter 4.2 Configuration of the guest systems contains the properties employed for the measurements used in this document Further information Optimal operation of ESXi server and VMWare Further information on the optimal operation is available on the support internet pages of VMWare under the following link. Enabled hardware for VMware The following internet address contains a summary of the hardware validated and enabled by VMWare. / Virtualization V1.0, Entry ID:

14 3 Procedure for the Virtualization 3.1 Process and required software 3 Procedure for the Virtualization Content This chapter shows you how to create virtual systems. 3.1 Process and required software Table 3-1 No. Step Virtualization SW SW 1. Establishing and creating the Management Station VMware Workstation or VMware Player VMware Converter VMware vsphere Creating the virtual system VMware Workstation or VMware Player 3. Installation and configuration of the operating system on the virtual system 4. Installation of on the virtual system 5. Installation and configuration of the virtualization server VMware ESXi and VMware vsphere client Depending on the application: Windows 2003 Windows 2008 Respective version depending on the application Transferring the virtual system onto the virtualization server VMware Converter and VMware ESXi 7. Adjusting the configuration of the virtual system to the virtualization server VMware ESXi and VMware vsphere client 8. Start and operation of the virtual system 9. Checking the system load of the virtual system and the virtualization server. 10. Operating the virtual system. Windows Remote Desktop. Note The VMware Workstation software is recommended for creating a virtual system. 14 / Virtualization V1.0, Entry ID:

15 3 Procedure for the Virtualization 3.2 Procedure in detail 3.2 Procedure in detail Note The procedure described here is only an example and represents one possible approach. Scenarios leading to the same result are also possible. Table 3-2 No. Step/Action 1. Establishing and creating the management station In addition to the virtualization server you require a PC in the same network as the virtualization server. Ensure that the following software has been installed on the management station. Operating system: or VMware vsphere VMware Converter or VMware Workstation VMware Workstation or VMware Player 2. Creating the virtual system on the management station Start the VMware Player. Select the Create a New Virtual Machine option. The New Virtual Machine Wizard appears. Here you select the point I will install the operating system later and click on Next. In the operation system field you select Microsoft Windows and in the Version field you select your respective operating system. Then click on Next. (Information on the operating system compatibilities are available in the FAQ with entry ID: ). Assign a unique name for your virtual system. Specify a local storage path and click on Next. (In the further course the virtual system is exclusively identified via this name.) Assign the hard disk size required for your combination and select the Store virtual disk as a single file option. Click on Next. An overview with the properties of the newly created virtual system appears. The properties must then still be adjusted! Click the Customize Hardware button. Another window with the option of configuring individual hardware components appears. Memory: here you assign the storage as specified in chapter systems. Processors: here you assign the number of processor cores as specified in chapter systems. CD/DVD: here you enter the physical drive you wish to use for installing the operating system and. Floppy: not mandatory, if it is not required remove the component with the Remove button. Network adapter: used here for the installation. (e.g. for activating the operating system.) Here in the Network connection field you select the type which is best for accessing your network. USB controller: is mandatory. (Installation of the license with USB stick.) Sound card: not mandatory, if no acoustic signaling is required remove this component with the Remove. / Virtualization V1.0, Entry ID:

16 3 Procedure for the Virtualization 3.2 Procedure in detail No. Step/Action Printer: not mandatory, if it is not required remove the component with the Remove button. Display: leave the settings. Add a second network cars if the virtual system shall have a terminal bus and a process bus. Confirm the Hardware window with OK. You are back in the window with the properties of the newly created virtual system. Click on Finish. You have now created a virtual system. 3. Installation and configuration of the operating system on the virtual system [management station] Create the installation medium for the operating system in the physical drive. Start the newly created virtual system by clicking on Play virtual machine. Now you see the boot process of the virtual system. The installation of the operating system is now offered to you. Start the installation of the operating system. Follow all instructions as for a classic installation. Configure the operating system after completing the installation. Installing the VMware tools. Configure the operating system according to the requirements of Release and the installation notes &TopicId= Install the required security patches. (Respective information is available in the FAQ with entry ID: Installation of on the virtual system [management station] Place the installation medium into the physical drive. Start the virtual system by clicking Play virtual machine. Start the installation of. Follow the instructions from Release and the installation notes & TopicId= Installation and configuration of the virtualization server The following steps require monitor and keyboard at the virtualization server. Place the VMware ESXi installation CD into the drive of the virtualization server and start it. In the BIOS you specify booting from CD. Follow the instructions of installation wizard. Perform the first basic configuration steps. Assign a root password. Adjust the network connection. 16 / Virtualization V1.0, Entry ID:

17 3 Procedure for the Virtualization 3.2 Procedure in detail No. Step/Action 6. Transferring the virtual system onto the virtualization server Variant (A) [VMware Converter on the management station] Ensure that the VMware Player has been connected. Start the VMware converter. Click on the Convert machine button. The Conversion dialog appears. Select the source type VMware Virtual Workstation and select your virtual system in the storage location of your virtual system. Click on Next. Select VMware Virtual Infrastructure Machine. Enter the user data defined in step 5 as well as the IP address of the ESXi virtualization server. Click on Next. Keep the name of your virtual system or assign a new name. Click on Next. In the item list you select your ESXi, the respective data storage (the physical drive on which the virtual system shall be stored) and the VMware version (typical Version 7 ). An overview appears with all parameters for transferring the virtual machine to the virtualization server. Check the parameters and, if necessary, change unsuitable points. Click on Next. A list with all settings made appears. Start the process by clicking on Finish. The conversion process begins. Variant (B) [only VMware Workstation on the management station] Ensure that your virtual system is not active. Start the Conversion Wizard via VMware Workstation > File > Import/Export. The Wizard appears. In the overview you click on Next. Another overview appears for step 1. Click on Next. Select Virtual Appliance from the dropdown list and click on Next. In the following dialog your select your virtual system and click on Next. Information on your virtual system is collected. In the following step of the Wizard you select all required hard drives of the system and click on Next. The overview for step 2 appears. Select VMware Infrastructure Virtual Machine as a target type and click on Next. Enter the user data defined in step 5 as well as the IP address of the ESXi virtualization server. Click on Next. The Conversion Wizard connects with the virtualization server. In the following dialog you assign a unique name for your virtual system. Now you select the used and click on Next. The hard disk information of the virtualization server is called up. Select your target drive and click on Next. The target parameters are checked. Assign the required networks and click on Next. The dialog for making userdefined settings appears. Deactivate the options and click on Next. An overview of the settings made appears. Deactivate the Power on the new virtual machine after creation option and click on Finish. / Virtualization V1.0, Entry ID:

18 3 Procedure for the Virtualization 3.2 Procedure in detail No. Step/Action 7. Adjusting the configuration of the virtual system to the virtualization server [management station] Start your VMware VSphere client. The log-on dialog appears: Enter the IP address of your virtualization server and your user data. The vsphere client starts. Select your transferred virtual system in the tree. In the right window pane you navigate to the Overview tab. In the Commands field you select the Edit settings entry. Check whether the assigned resources match the requirements from chapter systems. 8. Start and operation of the virtual system [management station] Start your VMware VSphere client. The log-on dialog appears: Enter the IP address of your virtualization server and your user data. The vsphere client starts. Select your transferred virtual system in the tree. Start your virtual system by clicking the Play button. Your system is now restarted. 9. Checking the system load of the virtual system and the virtualization server. [management station] Diagnostics information is available in chapter 6 Diagnostic Capabilities. 10. Operating the virtual system [management station] Ensure that your virtual system is active. Click Start > Run... Enter mstsc /? in the dialog. Check whether the option /console or /admin must be used to administer your virtual system. Confirm the dialog with OK. Click Start > Run... In the dialog you enter mstsc /admin or mstsc /console. Then the Windows Remote Desktop starts. Enter the Login data of your user. You can now use the virtual system as usual. 18 / Virtualization V1.0, Entry ID:

19 4 Framework Conditions for the Measurements 4.1 Hardware used Configuration 1, IPC 647C Table Framework Conditions for the Measurements 4.1 Hardware used Component ESX- 1 ESX- 2 Processor Intel Core i7-610e 2Cores/4Threads 2.53MHz cycle frequency with Turbo Boost 4MB Cache VT-d and EM64T as expanded command sets Intel Core i7-610e 2Cores/4Threads 2.53MHz cycle frequency with Turbo Boost 4MB Cache VT-d and EM64T as expanded command sets RAM 8 Gbytes DDR SD-RAM 8 Gbytes DDR SD-RAM Hard disks 2x 500GB 2x 1000GB Network cards 1x Onboard 82574L the only one accepted by VMware. 2x Intel PRO/1000GT (1000Base-T PCI), additionally plugged. The network cards were used as follows: Table 4-2 Network card Onboard 82574L Intel PRO/1000GT Intel PRO/1000GT Usage 1x Onboard 82574L the only one accepted by VMware. 2x Intel PRO/1000GT (1000Base-T PCI), additionally plugged. Management network e.g. for vspere access to ESXi Terminal Bus PLC Bus Note Further information on the used SIMATIC Industry PC is available in the following link. / Virtualization V1.0, Entry ID:

20 4 Framework Conditions for the Measurements 4.1 Hardware used Configuration 2, HP Blade System C7000 Enclosure G2 Two Blade ESXi servers as cluster. Table 4-3 Component Property Processor RAM Processor RAM Hard disks Used for ESXi Network cards 16 Cores (Intel Xeon Core i7 L5520, 2.27GHz) 192 GB 8 Cores (Intel Xeon Core i7 L5520, 2.27GHz) 98GByte No local hard disks, ESXi servers work with SAN (Storage Area Network). HP VC-Flags-10 ENET module 1GB (for management and communication with the PLCs). For this HP Blade System Resources can be dynamically combined and assigned. The above table shows that only a part of the resources are used. Note Further information on the used HP Blade system is available in the following link. Configuration 3, Fujitsu Primergy RX 300 S6 An ESXi server is used here. Table 4-4 Processor RAM Hard disks Component Property 12 Cores (Intel Xeon CPU GHz) 24 GB 6x 600GB SATA (local) Note Further information on the used Fujitsu Primergy system is available in the following link. Note When comparing the measuring data you will notice that the values of the better equipped HP Blade servers are slightly worse than those of the Fujitsu RX 300. This is, amongst other things, due to the fact that the ESX server on the Fujitsu RX 300 has over 12 CPUs. The ESX server of the HP Blade servers has only 8 CPUs available. 20 / Virtualization V1.0, Entry ID:

21 4.2 Configuration of the guest systems 4 Framework Conditions for the Measurements 4.2 Configuration of the guest systems Note For the settings of the guest systems please follow the installation notes and quantity frameworks of. Remote Desktop Protocol (RDP) The operating stations can be operated via an opened Remote Desktop connection. The measurements listed below were measured with opened Remote Desktop window. Note Remote Desktop must only be used via mstsc /console or mstsc /admin. Continuing information is available in chapter 3.2 Procedure in detail, in chapter 3.2 Procedure in detail in table section 5 Operating the virtual system. Reserved work memory for ESXi For secure operation a work memory of 2 GB must be reserved for the ESXi server. In configuration 1, IPC 647C there are 6 GB available for the virtualization. This requirement was not met in some of the following scenarios since the limits also had to be tested. (server operating system) Independent of whether Windows 2003 or Windows 2008 was used. Table 4-5 Hardware Setting RAM 3072MB CPUs 2 Graphics card 32MB Hard disk 1 Virtual hard disk, not dynamic Hard disk 2 Virtual hard disk, not dynamic CD/DVD drive ISO Image (with image of the DVD) Network adapter 1 Terminal bus Network adapter 2 PLC network Disk drive 1 device / Virtualization V1.0, Entry ID:

22 4 Framework Conditions for the Measurements 4.2 Configuration of the guest systems Figure 4-1 () Table 4-6 Hardware Setting RAM 2048 MB CPUs 2 Graphics card 32MB Hard disk 1 Virtual hard disk, not dynamic CD/DVD drive ISO Image (with image of the DVD) Network adapter 1 Terminal bus Disk drive 1 device ( SP3) Table 4-7 Hardware Setting RAM 1024MB CPUs 2 Graphics card 32MB VMCI device Hard disk 1 Virtual hard disk, not dynamic CD/DVD drive ISO Image (with image of the DVD) Network adapter 1 Terminal bus 22 / Virtualization V1.0, Entry ID:

23 4 Framework Conditions for the Measurements 4.3 Used software Hardware Setting Network adapter 2 Disk drive 1 PLC network device 4.3 Used software Operating systems Table 4-8 Type Operating system Windows 2003R2 with SP2 Windows 2008 (standard) with SP2 Professional +SP3 Note The measurements have yielded that the operating systems and Windows 2008 generally have a higher RAM demand than their predecessor. Released software Table 4-9 V7.0 with SP2 / /UserArchive /Redundancy /WebNavigator /DataMonitor /Connectivity Pack Product Note All further options of SIMATIC V7.0 SP2 are neither compatibility-tested nor approved for virtual environments. quantity framework/project Table 4-10 Criterion Property Number of connection with CPUs 2 Number of external S7 variables Curve archiving 4200 values/second / Virtualization V1.0, Entry ID:

24 4 Framework Conditions for the Measurements 4.3 Used software Criterion Message archiving UserAchive Picture change Property 8 messages/second 25 sets with two values in 5 seconds In 5 seconds interval; Or whichever deviating value is given in the subsequent tests. 24 / Virtualization V1.0, Entry ID:

25 4.3 Used software 5 Test Scenarios and Basic Performance Data Determining the basic performance data of the guest systems The values shown in the subsequent test scenarios were determined in two different ways. It is differentiated between... system (determined CPU values and active RAM with vsphere.) system (determined values in the operating system using the performance monitor.) The example in the following graphic displays the monitoring of the guest system with the performance monitor (in the operating system). Using the Microsoft performance monitor enables simple monitoring of the processes and the storage consumption in the operating system. Figure 5-1 Determining the basic performance data of the ESXi server When monitoring the ESXi server the following recordings were made in the test scenarios: CPU load Active work memory / Virtualization V1.0, Entry ID:

26 4.3 Used software Interpretation of the measured values The following graphic represents an overloaded ESXi server. (Due to the overload the recording of archived data was stopped temporarily.) Note A CPU load of 75% should not be exceeded permanently. Figure / Virtualization V1.0, Entry ID:

27 5.1 standalone 5.1 standalone Overview The figure below shows a schematic illustration of the virtual components of this solution. Two measurements are performed (with Windows 2008 server and Windows 2003 server). The SIMATIC IPC 647C is used as the test platform. Figure 5-3 Win 2008 Win 2003 ESXi (1) ESXi (2) Basic performance data Table 5-1 PC IPC 647C: ESXi (1) / SIMATIC IPC 647C SIMATIC IPC 647C PC Ø CPU in % Max. CPU in % Active RAM ESXi (1) 36% 58% 1.3 GB (max. 2 GB) Win 2008 Win % 57% 1.2 GB (max. 1.9 GB) 25% 50% 1.9 GB IPC 647C: EXSi (2) ESXi (2) 39% 65% 665 MB (max. 1.3 GB) Win 2003 Win % 64% 595 MB (max. 1.2 GB) 27% 44% 1.4 GB Conclusion Using Windows 2008 requires more storage on the ESXi server. This also applies for the client operating system. / Virtualization V1.0, Entry ID:

28 5.2 and one 5.2 and one Overview The figure below shows a schematic illustration of the virtual components of this solution. Two measurements are performed (with Windows 2008 server and Windows 2003 server). The SIMATIC IPC 647C is used as the test platform. Figure 5-4 Win 2008 Win 2003 ESXi (1) ESXi (2) SIMATIC IPC 647C SIMATIC IPC 647C Description Operations occur at the server and the client. On both stations pictures change in 5 seconds intervals for simulating an operation. Basic performance data Table 5-2 PC IPC 647C: ESXi (1) IPC 647C: EXSi (2) / PC Ø CPU in % Max. CPU in % Active RAM ESXi (1) 56% 85% 1.4GB (max. 2GB) Win 2008 Win % 59% 1GB (max. 1.6GB) 21% 35% 235MB (max. 315MB) 29% 59% 1.9GB 11% 19% 485MB EXSi (2) 59% 90% 970MB (max. 1.6GB) Win 2003 Win % 61% 220MB (max. 515MB) 21% 40% 320MB (max. 515MB) 37% 63% 1.4GB 14% 24% 490GB 28 / Virtualization V1.0, Entry ID:

29 5.3 and two Standard s 5.3 and two Standard s Overview The figure below shows a schematic illustration of the virtual components of this solution. Two measurements are performed per virtualization server (with Windows 2008 and Windows 2003 ). The test platforms are: SIMATIC IPC 647C HP Blade Fujitsu Primergy Figure 5-5 Win 2008 ESXi (1) SIMATIC IPC 647C Win 2003 ESXi (2) SIMATIC IPC 647C Win 2008 Win 2003 ESXi (1) ESXi (2) HP Blade Win 2008 Win 2003 ESXi (1) Fujitsu Primergy ESXi (2) Fujitsu Primergy / Virtualization V1.0, Entry ID:

30 5.3 and two Standard s Description Operator actions occur at the server and both clients. On both stations pictures change in 5 seconds intervals for simulating an operation. Basic performance data Table 5-3 PC / PC Ø CPU in % Max. CPU in % Active RAM ESXi (1) 70% 92% 2.2GB (max. 2.7GB) Win % 51% 1.4GB (max. 1.9GB) 19% 40% 210MB (max. 305MB) IPC 647C: ESXi (1) IPC 647C: EXSi (2) Win % 41% 455MB (max. 965MB) 39% 70% (max. 2.7GB) 20% 30% (max. 2.7GB) 16% 60% (max. 2.7GB) EXSi (2) 78% 100% 2.0 GB (max. 2.8GB) Win 2003 Win % 63% 770MB (max. 1.3GB) 23% 40% 320MB (max. 515MB) 16% 26% 800MB (max. 1GB) 51% 74% (max. 2.7GB) 18% 45% (max. 2.7GB) 14% 40% (max. 2.7GB) ESXi 17% 27% 2 GB (max. 2.4GB) Win % 57% 975MB (max. 1.3GB) 20% 40% 220MB (max. 295MB) HP Blade: ESXi (1) Win % 31% 840MB (max. 1GB) 36% 67% 1.6 GB 19% 34% 460 MB 14% 26% 880 MB 30 / Virtualization V1.0, Entry ID:

31 5.3 and two Standard s PC / PC Ø CPU in % Max. CPU in % Active RAM ESXi 17% 26% 1.6GB (max. 2GB) Win % 59% 535MB (max. 880MB) 17% 36% 180MB (max. 285MB) HP Blade: ESXi (2) Win % 30% 800MB (max. 1.1GB) 42% 51% 1.2 GB 17% 36% 500 MB 11% 25% 860 MB ESXi 11% 19% 1.9GB (max. 2.4GB) Win % 50% 1.3GB (max. 1.6GB) Fujitsu Primergy: ESXi (1) Win % 38% 215MB (max. 515MB) 12% 28% 405MB (max. 525MB) 23% 42% 1.6 GB 12% 24% 465 MB 7% 13% 910 MB ESXi 11% 18% 1.3GB (max. 1.9GB) Win % 48% 670MB (max. 1GB) Fujitsu Primergy: ESXi (2) Win % 39% 215MB (max. 305MB) 12% 29% 400MB (max. 600MB) 26% 36% 1.3GB 12% 23% 480MB 7% 14% 920MB Conclusion SIMATIC IPC 647C This configuration puts considerable load on the ESXi server on the SIAMTIC IPC 647C. ATTENTION A permanent operation in this constellation is not recommended. / Virtualization V1.0, Entry ID:

32 5.4 and three Standard s Conclusion for HP Blade server and Fujitsu Primergy RX 300 Both computers in this configuration are not used to capacity. The active storage requirement is equally high as for SIMATIC IPC 647C. The basic performance data of the operating systems remain almost identical, the configuration of the guest systems remains unchanged. 5.4 and three Standard s Overview The figure below shows a schematic illustration of the virtual components of this solution. For each virtualization server two measurements are performed (with Windows 2008 and Windows 2003 ). The test platforms are: SIMATIC IPC 647C HP Blade Fujitsu Primergy Figure 5-6 Win 2008 ESXi (1) Win 2003 ESXi (2) SIMATIC IPC 647C SIMATIC IPC 647C Win 2008 Win 2003 ESXi (1) ESXi (2) HP Blade 32 / Virtualization V1.0, Entry ID:

33 5.4 and three Standard s Win 2008 Win 2003 ESXi (1) Fujitsu Primergy ESXi (2) Fujitsu Primergy Description The clients are standard clients. There is no operation at the server, on the clients pictures change every 5 seconds. Basic performance data PC / Computer Ø CPU in % Max. CPU in % Active RAM ESXi (1) 76% 100% 2.8 GB (max. 3.7 GB) Win % 45% 1 GB (max. 1.4 GB) 14% 41% 570 MB (max. 725 MB) 15% 31% 595 MB (max. 755 MB) 16% 30% 515 MB (max. 1.1 GB) ICP 647C: ESXi (1) Win % 80% 1.9 GB 12% 51% 510 MB 17% 36% 510 MB 14% 59% 950 MB / Virtualization V1.0, Entry ID:

34 5.4 and three Standard s PC / Computer Ø CPU in % Max. CPU in % Active RAM EXSi (2) 73% 100% 2 GB (max. 2.8 GB) Win % 48% 620 MB (max. 1 GB) 19% 35% 430 MB (max. 525 MB) 13% 32% 565 MB (max. 675 MB) 10% 16% 320 MB (max. 525 MB) ICP 647C: EXSi (2) Win % 80% 1.9 GB 12% 51% 510 MB 17% 36% 510 MB 14% 59% 950 MB ESXi 19% 28% 2.3 GB (max. 2.7 GB) HP Blade: ESXi (1) Win 2008 Win % 43% 1.2 GB (max. 1.6 GB) 13% 22% 215 MB (max. 315 MB) 15% 38% 215 MB (max. 305 MB) 19% 32% 670 MB (max. 880 MB) 32% 54% 1.5 GB 10% 16% 460 MB 14% 41% 460 MB 13% 26% 890 MB ESXi 20% 29% 1.5 GB (max. 2 GB) Win % 39% 455 MB (max. 720 MB) 19% 33% 220 MB (max. 325 MB) 15% 34% 225 MB (max. 400 MB) 11% 35% 545 MB (max. 880 MB) HP Blade: ESXi (2) Win % 54% 1.1 GB 10% 16% 460 MB 14% 41% 460 MB 13% 26% 870 MB 34 / Virtualization V1.0, Entry ID:

35 5.4 and three Standard s PC / Computer Ø CPU in % Max. CPU in % Active RAM ESXi 11% 19% 1.8 GB (max. 2.3 GB) Win % 34% 1.2 GB (max. 1.6 GB) 11% 16% 150 MB (max. 230 MB) 14% 43% 180 MB (max. 315 MB) Fujitsu Primergy: ESXi (1) Win % 29% 330 MB (max. 590 MB) 17% 29% 1.5 GB 7% 10% 460 MB 8% 24% 480 MB 7% 14% 910 MB Fujitsu Primergy: ESXi (2) ESXi 12% 19% 1.3 GB (max. 2 GB) Win 2008 Win % 38% 490 MB (max. 690 MB) 18% 41% 205 MB (max. 350 MB) 14% 39% 205 MB (max. 295 MB) 9% 11% 305 MB (max. 465 MB) 20% 29% 1.2 GB 11% 21% 470 MB 9% 20% 485 MB 4% 6% 900 MB Conclusion for SIMATIC IPC 647C This configuration puts considerable load on the IPC 647C, the user must expect long delays when updating pictures. This also applies to updating the TagLogging and AlarmLogging controls. When reading data from the archive (selection of TagLogging picture) the CPU load of the ESXi server goes to 100% depending on the data volume. ATTENTION Operation in this constellation is not recommended. / Virtualization V1.0, Entry ID:

36 5.5 on ESXi (1) and four s on ESXi (2) 5.5 on ESXi (1) and four s on ESXi (2) on ESXi (1) and four Standard s on ESXi (2) Overview The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: SIMATIC IPC 647C HP Blade Figure 5-7 Win 2008 ESXi (1) SIMATIC IPC 647C ESXi (2) SIMATIC IPC 647C Win 2008 ESXi (1) ESXi (2) HP Blade Description No operation occurs at the server. The clients are standard clients. 36 / Virtualization V1.0, Entry ID:

37 5.5 on ESXi (1) and four s on ESXi (2) Basic performance data PC / Computer Ø CPU in % Max. CPU in % Active RAM IPC 647C: ESXi (1) ESXi (1) 33% 55% 1.2 GB (max GB) Win 2008 Win % 54% 1.1 GB (max. 1.7 GB) 31% 45% 1.9 GB EXSi (2) 60% 80% 1.6 GB (max. 1.9 GB) 11% 13% 440 MB (max. 570 MB) 14% 28% 400 MB (max. 545 MB) 20% 34% 215 MB (max. 295 MB) IPC 647C: EXSi (2) HP Blade: ESXi (1) 13% 35% 485 MB (max. 590 MB) 10% 14% 915 MB 14% 40% 955 MB 20% 31% 485 MB 15% 31% 490 MB ESXi 8% 16% 1.5 GB (max. 2 GB) Win 2008 Win % 52% 1.1 GB (max. 1.5 GB) 29% 62% 1.8 GB ESXi 15% 26% 1 GB (max. 1.4 GB) 11% 14% 320 MB (max. 482 MB) 14% 27% 320 MB (max. 440 MB) HP Blade: ESXi (2) 18% 32% 203 MB (max. 294 MB) 14% 24% 200 MB (max. 252 MB) 9% 14% 1 GB 14% 21% 1 GB / Virtualization V1.0, Entry ID:

38 5.5 on ESXi (1) and four s on ESXi (2) PC / Computer Ø CPU in % Max. CPU in % Active RAM 20% 38% 560 MB 15% 31% 560 MB 38 / Virtualization V1.0, Entry ID:

39 5.5 on ESXi (1) and four s on ESXi (2) on ESXi (1) and four Multi s on ESXi (2) Overview The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: SIMATIC IPC 647C HP Blade Figure 5-8 Win 2008 Win 2008 ESXi (1) SIMATIC IPC 647C ESXi (2) SIMATIC IPC 647C ESXi (1) ESXi (2) HP Blade Description No operation occurs at the server. The clients are multi clients. / Virtualization V1.0, Entry ID:

40 5.5 on ESXi (1) and four s on ESXi (2) Basic performance data PC / Computer Ø CPU in % Max. CPU in % Active RAM IPC 647C: ESXi (1) ESXi (1) 37% 55% 1.3 GB (max. 1.9 GB) Win 2008 Win % 54% 1.2 GB (max. 1.8 GB) 30% 44% 1.9 GB EXSi (2) 69% 89% 1.8 GB (max. 2.2 GB) 15% 30% 460 MB (max. 650 MB) 10% 27% 485 MB (max. 675 MB) 16% 35% 390 MB (max. 475 MB) IPC 647C: EXSi (2) HP Blade: ESXi (1) 18% 33% 410 MB (max. 570 MB) 10% 30% 975 MB 15% 30% 990 MB 20% 28% 565 MB 16% 38% 550 MB ESXi 8% 17% 1.5 GB (max. 2 GB) Win 2008 Win % 43% 1.1 GB (max. 1.6 GB) 28% 50% 1.6 GB ESXi 15% 23% 1 GB (max. 1.3 GB) 11% 14% 330 MB (max. 505 MB) 14% 27% 340 MB (max. 505 MB) HP Blade: ESXi (2) 18% 24% 205 MB (max. 295 MB) 13% 37% 185 MB (max. 275 MB) 8% 14% 1 GB 14% 27% 1 GB 40 / Virtualization V1.0, Entry ID:

41 5.5 on ESXi (1) and four s on ESXi (2) PC / Computer Ø CPU in % Max. CPU in % Active RAM 19% 30% 580 MB 14% 38% 570 MB Conclusion As apparent in the following measurements in chapters to standard clients require more active RAM than multi clients. / Virtualization V1.0, Entry ID:

42 5.5 on ESXi (1) and four s on ESXi (2) and four Standard s Overview The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: HP Blade Fujitsu Primergy Figure 5-9 Win 2008 Win 2008 ESXi HP Blade ESXi Fujitsu Primergy Description No operation occurs at the server. The clients are standard clients with operation. 42 / Virtualization V1.0, Entry ID:

43 5.5 on ESXi (1) and four s on ESXi (2) Basic performance data PC / Computer Ø CPU in % Max. CPU in % Active RAM ESXi 24% 39% 2.9 GB (max. 3.4 GB) Win % 44% 1.3 GB (max. 1.6 GB) 14% 26% 685 MB (max. 880 MB) 13% 27% 470 MB (max. 610 MB) 18% 34% 185 MB (max. 350 MB) 17% 36% 205 MB (max. 360 MB) Win % 55% 1.6 GB 11% 15% 900 MB HP Blade 13% 27% 880 MB 19% 37% 470 MB 16% 38% 470 MB ESXi 13% 22% 2.2 GB (max. 2.6 GB) Win % 44% 1.1 GB (max. 1.4 GB) 8% 11% 240 MB (max. 380 MB) 12% 39% 375 MB (max. 715 MB) 18% 34% 200 MB (max. 305 MB) 14% 39% 190 MB (max. 325 MB) Win % 32% 1.4 GB 4% 6% 910 MB Fujitsu Primergy 8% 33% 900 MB 13% 23% 475 MB 8% 26% 485 MB / Virtualization V1.0, Entry ID:

44 5.5 on ESXi (1) and four s on ESXi (2) and four Multi s on one ESXi Overview The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: HP Blade Fujitsu Primergy Figure 5-10 Win 2008 Win 2008 ESXi HP Blade ESXi Fujitsu Primergy Description No operation occurs at the server. The clients are multi clients with operation. 44 / Virtualization V1.0, Entry ID:

45 5.5 on ESXi (1) and four s on ESXi (2) Basic performance data PC / Computer Ø CPU in % Max. CPU in % Active RAM ESXi 22% 40% 2.4 GB (max. 2.8 GB) Win % 46% 1.1 GB (max. 1.5 GB) 10% 80% 430 MB (max. 695 MB) 13% 30% 365 MB (max. 570 MB) 18% 32% 225 MB (max. 325 MB) 16% 35% 210 MB (max. 315 MB) Win % 67% 1.7 GB 8% 68% 1 GB HP Blade 13% 23% 1 GB 18% 32% 580 MB 16% 35% 590 MB ESXi 13% 22% 2.3 GB (max. 2.8 GB) Win % 40% 1.2 GB (max. 1.5 GB) 9% 12% 330 MB (max. 550 MB) 12% 22% 320 MB (max. 485 MB) 17% 35% 230 MB (max. 305 MB) 14% 40% 205 MB (max. 285 MB) Win % 36% 1.6 GB 4% 7% 1 GB Fujitsu Primergy 6% 10% 1 GB 12% 21% 590 MB 8% 23% 580 MB / Virtualization V1.0, Entry ID:

46 5.5 on ESXi (1) and four s on ESXi (2) on ESXi (1) and five Standard s on ESXi (2) Overview The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: SIMATIC IPC 647C HP Blade Figure 5-11 Win 2008 Win 2008 ESXi (1) SIMATIC IPC 647C ESXi (2) SIMATIC IPC 647C ESXi (1) ESXi (2) HP Blade Description Test scenarios and illustrate the effects of the picture change to the CPU load of the server. An additional client is added for these tests. The additional client with its picture changes produces a higher load at the server. No operation occurs at the server. The clients are standard clients. 46 / Virtualization V1.0, Entry ID:

47 5.5 on ESXi (1) and four s on ESXi (2) Basic performance data PC / Computer Ø CPU in % Max. CPU in % Active RAM IPC 647C: ESXi (1) ESXi (1) 39% 57% 1.45 GB (max. 1.8 GB) Win 2008 Win % 56% 1.4 GB (max. 1.7 GB) 37% 46% 1.9 GB EXSi (2) 81% 100% 2 GB (max. 2.4 GB) 15% 26% 520 MB (max. 665 MB) 14% 23% 425 MB (max. 630 MB) 17% 30% 200 MB (max. 305 MB) 16% 31% 470 MB (max. 580 MB) IPC 647C: EXSi (2) 18% 32% 325 MB (max. 430 MB) 15% 43% 940 MB 14% 57% 960 MB 22% 42% 485 MB 22% 53% 495 MB 20% 47% 450 MB HP Blade: ESXi (1) ESXi 9% 17% 1.8 GB (max. 2.2 GB) Win 2008 Win % 53% 1.4 GB (max. 1.8 GB) 33% 61% 1.8 GB ESXi 22% 31% 1.4 GB (max. 1.9 GB) 14% 28% 355 MB (max. 485 MB) HP Blade: ESXi (2) 14% 30% 320 MB (max. 505 MB) 19% 35% 215 MB (max. 305 MB) 17% 31% 210 MB (max. 275 MB) 19% 35% 215 MB (max. 545 MB) / Virtualization V1.0, Entry ID:

48 5.5 on ESXi (1) and four s on ESXi (2) PC / Computer Ø CPU in % Max. CPU in % Active RAM 33% 61% 1.8 GB 14% 27% 1 GB 14% 28% 1 GB 21% 35% 570 MB 20% 35% 560 MB 48 / Virtualization V1.0, Entry ID:

49 5.5 on ESXi (1) and four s on ESXi (2) on ESXi (1) and five Standard s on ESXi (2) Overview The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: SIMATIC IPC 647C HP Blade Figure 5-12 Win 2008 Win 2008 ESXi (1) SIMATIC IPC 647C ESXi (2) SIMATIC IPC 647C ESXi (1) ESXi (2) HP Blade Description No operation occurs at the server. The clients are standard clients, a picture change occurs every 20 seconds. / Virtualization V1.0, Entry ID:

50 5.5 on ESXi (1) and four s on ESXi (2) Basic performance data PC / Computer Ø CPU in % Max. CPU in % Active RAM IPC 647C: ESXi (1) ESXi (1) 31% 55% 1 GB (max. 1.7 GB) Win 2008 Win % 54% 950 MB (max. 1.6 GB) 35% 45% 1.9 GB EXSi (2) 59% 88% 1.9 GB (max. 2.5 GB) 11% 31% 470 MB (max. 650 MB) 9% 31% 370 MB (max. 545 MB) 13% 38% 310 MB (max. 485 MB) IPC 647C: EXSi (2) 11% 33% 445 MB (max. 570 MB) 14% 26% 215 MB (max. 370 MB) 10% 25% 940 MB 11% 45% 955 MB 14% 29% 490 MB 12% 21% 490 MB 13% 19% 455 MB HP Blade: ESXi (1) ESXi 8% 16% 1.5 GB (max. 1.9 GB) Win 2008 Win % 48% 1.1 GB (max. 1.4 GB) 30% 76% 1.8 GB ESXi 17% 38% 1.4 GB (max. 2.2 GB) HP Blade: ESXi (2) 10% 47% 320 MB (max. 400 MB) 12% 99% 440 MB (max. 1GB) 14% 45% 195 MB (max. 325 MB) 12% 45% 230 MB (max. 370 MB) 50 / Virtualization V1.0, Entry ID:

51 5.5 on ESXi (1) and four s on ESXi (2) PC / Computer Ø CPU in % Max. CPU in % Active RAM 15% 46% 185 MB (max. 275 MB) 9% 48% 1 GB 10% 65% 1 GB 14% 42% 570 MB 13% 50% 560 MB 12% 45% 500 MB Conclusion Strong CPU load of the server for fast, continued picture changes. Increasing the CPU load at / and the active work memory when selecting pictures with TagLogging and AlarmLogging controls for which values need to be read from the archive. Increasing CPU load also causes increased storage demand. / Virtualization V1.0, Entry ID:

52 5.5 on ESXi (1) and four s on ESXi (2) and six Standard s on one ESXi Overview The figure below shows a schematic illustration of the virtual components of this solution. The HP Blade server is used as the test platform. Figure 5-13 Win 2008 ESXi Win 2008 ESXi HP Blade Fujitsu Primergy Description No operation occurs at the server. The clients are standard clients with operation. Basic performance data PC HP Blade / Computer Ø CPU in % Max. CPU in % Active RAM ESXi 30% 39% 3.5 GB (max. 4.3 GB) Win % 43% 1.3 GB (max. 1.6 GB) 14% 28% 690 MB (max. 880 MB) 52 / Virtualization V1.0, Entry ID:

53 5.5 on ESXi (1) and four s on ESXi (2) PC / Computer Ø CPU in % Max. CPU in % Active RAM 11% 36% 370 MB (max. 545 MB) 12% 34% 410 MB (max. 610 MB) 17% 33% 190 MB (max. 260 MB) 15% 31% 200 MB (max. 260 MB) 13% 17% 180 MB (max. 325 MB) Win % 61% 1.5 GB 13% 25% 900 MB 12% 52% 900 MB 9% 43% 880 MB 20% 37% 470 MB 17% 39% 470 MB 13% 19% 470 MB ESXi 19% 28% 2.8 GB (max. 3.4 GB) Win % 40% 1.3 GB (max. 1.6 GB) 12% 27% 315 MB (max. 465 MB) 10% 24% 300 MB (max. 485 MB) 11% 18% 330 MB (max. 610 MB) 17% 38% 205 MB (max. 305 MB) 18% 35% 195 MB (max. 275 MB) 12% 18% 165 MB (max. 255 MB) Win % 33% 1.4 GB 7% 13% 930 MB Fujitsu Primergy 5% 17% 900 MB 3% 8% 880 MB 13% 23% 480 MB / Virtualization V1.0, Entry ID:

54 5.5 on ESXi (1) and four s on ESXi (2) PC / Computer Ø CPU in % Max. CPU in % Active RAM 9% 26% 500 MB 7% 11% 450 MB 54 / Virtualization V1.0, Entry ID:

55 5.5 on ESXi (1) and four s on ESXi (2) and six Multi s on one ESXi Overview The figure below shows a schematic illustration of the virtual components of this solution. The HP Blade server is used as the test platform. Figure 5-14 Win 2008 ESXi Win 2008 ESXi HP Blade Fujitsu Primergy Description No operation occurs at the server. The clients are standard clients with operation. Basic performance data PC HP Blade / Computer Ø CPU in % Max. CPU in % Active RAM ESXi 28% 36% 3 GB (max. 3.6 GB) Win % 48% 1.3 GB (max. 1.9 GB) 14% 29% 490 MB (max. 690 MB) / Virtualization V1.0, Entry ID:

56 5.5 on ESXi (1) and four s on ESXi (2) PC / Computer Ø CPU in % Max. CPU in % Active RAM 10% 30% 315 MB (max. 440 MB) 11% 40% 295 MB (max. 480 MB) 17% 23% 220 MB (max. 315 MB) 15% 36% 210 MB (max. 315 MB) 13% 39% 205 MB (max. 265 MB) Win % 68% 1.7 GB 13% 25% 1 GB 10% 33% 1 GB 9% 40% 1 GB 19% 34% 580 MB 14% 38% 580 MB 13% 38% 565 MB ESXi 18% 28% 2.9 GB (max. 3.5 GB) Win % 41% 1.3 GB (max. 1.5 GB) 12% 25% 360 MB (max. 525 MB) 10% 29% 325 MB (max. 505 MB) 12% 40% 310 MB (max. 485 MB) 17% 35% 210 MB (max. 305 MB) 18% 41% 230 MB (max. 380 MB) 13% 55% 215 MB (max. 305 MB) Win % 38% 1.6 GB 8% 13% 1 GB Fujitsu Primergy 5% 17% 1 GB 4% 24% 1 GB 12% 21% 590 MB 56 / Virtualization V1.0, Entry ID: