VMware VIEW COMPOSER 2.5 - ARCHITECTURE Manual de usuario Pagina 38

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 73
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 37
EMC Infrastructure for Virtual Desktops Enabled by EMC VNX Series,
VMware vSphere 4.1, VMware View 4.5, and VMware View Composer 2.5 Proven Solution Guide
38
Microsoft Word 2007One instance to measure the response time and one
instance to edit the document.
Bullzip PDF Printer and Acrobat ReaderThe Word document was printed and the
PDF was reviewed.
Microsoft Excel 2007A very large sheet was opened and random operations
were performed.
Microsoft PowerPoint 2007—A presentation was reviewed and edited.
7-zipUsing the command line version, the output of the session was zipped.
Login VSI
launcher
A Login VSI launcher is a Windows system that launches desktop sessions on target
virtual desktops. There are two types of launchersmaster and slave. There is only
one master in a given test bed and there can be as many slave launchers as
required.
The number of desktop sessions a launcher can run is typically limited by the CPU or
memory resources. Login consultants recommend using a maximum of 45 sessions
per launcher with two CPU cores (or two dedicated vCPUs) and 2 GB RAM, when
the GDI limit has not been tuned (default). However with the GDI limit tuned, this limit
extends to 60 sessions per two-core machine.
In this validated testing, 500 desktop sessions were launched from 12 launcher
virtual machines, resulting in approximately 42 sessions established per launcher.
Each launcher virtual machine is allocated two vCPUs and 4 GB of RAM. There
were no bottlenecks observed on the launchers during the VSI-based tests.
FAST Cache
configuration
For all tests, FAST Cache was enabled for the storage pool holding the four Pool1_x
data stores. FAST Cache is not enabled for the EFD-based replica image.
Replica storage
configuration
Two LUNs were created on two EFDs with a RAID 1/0 configuration for hosting
replica data stores. The replicas were split across both SPs for the load balancing.
Read cache is enabled on the LUNs.
Result analysis
Introduction
This section explains the results for the different test scenarios.
Boot storm results
Test
methodology
This test was conducted by selecting all the desktops in vCenter Server and
selecting Power On. Overlays are added to the graphs to show when the last power-
on task completed and when the IOPS to the pool LUNs achieved a steady state.
For the boot storm test, all the desktops were powered on within 8 minutes and
achieved steady state approximately 3 minutes later. The total start-to-finish time
was approximately 11 minutes.
Vista de pagina 37
1 2 ... 33 34 35 36 37 38 39 40 41 42 43 ... 72 73

Comentarios a estos manuales

Sin comentarios