VMworld 2014 Session Notes: EUC1653 — Horizon 6 Hosted Applications Technical Deep Dive

Below are my notes from VMworld Session EUC1653 by Andrew Johnson and Warren Ponder entitled “Horizon 6 Hosted Applications Technical Deep Dive” All credit for the material below belongs to the tremendous authors/speakers, Andrew Johnson and Warren Ponder of VMware.

  • View AppTap: Enumerates installed/removed/changes apps on the RDS hosts, reports apps installed on the RDS host to View including PNG icons, product name and version, and path.
  • VMWProtocolManager: Interface that lets VMware plug into RDS, very well integrated and supported by Microsoft.
  • VMware took the Unity code from VMware Workstation for RDS Integration for View.
  • In 1.0, RDS is missing: USB Redirection, Printing (in next release), 3D Graphics, Multi-Site Routing/Failover
  • Can launch apps via View Client or Horizon Workspace
  • If you just want apps, there is no requirement to do vCenter integration, Composer, desktop functionality/setup, etc.
  • Client App Request Basic Load Balancing
  • New client requests an app from a farm
  • Farm consists of two hosts
  • Host #1, Max Session Cap = 100, 50 Active Sessions
  • Host #2, Max Session Cap = 50, 25 Active Sessions
  • Client gets sent to Host #1 as it has the most active session slots (Session Slots = Session Cap — Active Sessions).
  • Same PCoIP tuning and metrics are still valid.
  • Host Sizing and Common Practices
  • Each RDS host is configured with a maximum session limit (150 is default, but configurable)
  • Size each RDS Farm with Identical Sized Hosts
  • All RDS hosts within a farm should contain the same applications with the same configuration (Executable paths must be the same!)
  • Less powerful RDS hosts can be configured with a lower session limit
  • Common RDS Design Considerations
  • Use Group Policies to secure and harden the RDS hosts.
  • ‘Empty Session’ timeout is 1 minute by default
  • Configure using Group Policy to log off disconnected sessions after a specified time (e.g. 1 day)
  • Both App Pools & Desktop Pools can use the same RDS Farm
  • If an RDS hosted desktop and remote app are launched, two sessions will be established to the same host.
  • Lessons Learned for RDSH Sizing
  • One a 4x 8-core socket system testing with View Planner 3.5:
  • 8 x 8 vCPU VMs provide the best performance
  • 2:1 CPU over-commitment provided best performance
  • Scale out, not up
  • Allocate CPU/memory that will fit in the NUMA node
  • Resources per session (conservative estimates on medium workload)
  • CPU: 300–500MHz per session
  • Memory: 400–500MB per user
  • Disk space: 200–300MB per user in OS disk for profiles, temp files, etc.
  • Network: 50 kbps per session
  • Common Best Practices
  • Don’t overcommit CPU (e.g. more vCPU than logical cores)
  • Enable Hyper-Threading
  • Do not Disable ASLR
  • Enable Transparent Page Sharing
  • Enable Fixed Memory Allocation
  • Disable BIOS level CPU Power Saving
Show your support

Clapping shows how much you appreciated Earl Gay’s story.