27
Citrix TechXperts Perth - May 2016 JEREMY SAUNDERS [email protected] 0413 441 846

Citrix TechXperts Perth May 2016

Embed Size (px)

Citation preview

Page 1: Citrix TechXperts Perth May 2016

Citrix TechXpertsPerth - May 2016

JEREMY [email protected] 441 846

Page 2: Citrix TechXperts Perth May 2016

Agenda◦Intel Processors◦PowerShell Scripts

Page 3: Citrix TechXperts Perth May 2016

Intel Processors◦NUMA - Why is it SO important?◦Cluster-On-Die – The Snoop Mode or Snoop Dogg.◦To Hyper-thread or not - that is the question.◦Oversubscription of vCPU to pCPU – you better pause and think about it before your hosts do!

Page 4: Citrix TechXperts Perth May 2016

NUMA◦NUMA is Non-Uniform Memory Access◦It was first introduced in 2007 (circa) with the 1st generation Core i-series Nahalem processors.

Page 5: Citrix TechXperts Perth May 2016

Non-Uniform? Is that like casual dress Friday for RAM?◦Memory access times are NOT uniform and depend on the location of the memory and the node from which it is accessed.

Page 6: Citrix TechXperts Perth May 2016

Why did Intel move to a NUMA Model?

Page 7: Citrix TechXperts Perth May 2016

Intel Haswell and now Broadwell Processors

◦Nahalem & Sandy Bridge processors were a great leap forward.

◦Ivy Bridge, still in many systems today.◦The Haswell and now Broadwell families are outstanding technology when building a High Performance Computing (HPC) platform.

Page 8: Citrix TechXperts Perth May 2016

Intel Tock Tick Development Cycle

Page 9: Citrix TechXperts Perth May 2016

Haswell EP 2600 V3 Block DiagramMCC 12C/HCC 14C

Page 10: Citrix TechXperts Perth May 2016

Snoop Mode Performance Taken from two White Papers:

1) FUJITSU Server PRIMERGY Memory Performance of Xeon E5-2600 v4 (BroadwellEP) based Systems2) FUJITSU Server PRIMERGY Memory Performance of Xeon E5-2600 v3 (HaswellEP) based Systems

Page 11: Citrix TechXperts Perth May 2016

Haswell EP 2600 V3 Block Diagram with COD

MCC 12C/HCC 14C

Page 12: Citrix TechXperts Perth May 2016

Broadwell EP 2600 V4 Block DiagramMCC 12C/HCC 16C

Page 13: Citrix TechXperts Perth May 2016

Broadwell EP 2600 V4 Block Diagram with COD

MCC 12C/HCC 16C

Page 14: Citrix TechXperts Perth May 2016

Hyper-threading◦ It was designed to increase parallelism in a compute environment that

is I/O-bound (non-CPU intensive).◦ When enabled hyper-threading presents twice the number of logical

cores to the Operating System.◦ Allows for the parallel execution of multiple threads on the same

physical core.◦ But each physical core contains only a single execution resource.◦ So the two threads scheduled on the same physical core are effectively

sharing the execution resource and clock cycles.◦ Not only this, but the parallel executions run in lockstep.

Page 15: Citrix TechXperts Perth May 2016

Hyper-threading – Continued…

◦One logical core represents the physical core and the other represents its hyper-threaded twin. This twin runs at approximately 30% of the performance of the physical one.

◦The CPU Scheduler of any modern Operating System (and Hypervisor) is hyper-threading aware.

◦Application Vendors can query the Operating System to return the real physical cores and ensure their threads are prioritised to these where possible.

Page 16: Citrix TechXperts Perth May 2016

Hyper-threading – Continued…

http://wahlnetwork.com/2013/09/30/hyper-threading-gotcha-virtual-machine-vcpu-sizing/

Page 17: Citrix TechXperts Perth May 2016

The Analogy of Hyper-threading

Page 18: Citrix TechXperts Perth May 2016

Over-subscription◦Having multiple VMs that, when combined, exceed the number of physical cores means that you’re overcommitting the CPU resources.

◦Citrix say that the CPU over-subscription sweet spot is likely somewhere in between 1.5 and 2x.

◦I believe you should be starting at no more than 1.5.

Page 19: Citrix TechXperts Perth May 2016

Over-subscription – Continued…

I much prefer to follow a formula from Andy Morgan.◦ Each physical core = 1◦ Each HT core = 0.25◦ Reserve at least one core for hypervisor◦ Don't overcommit until you're running your production workload and can view impact.

The minute you introduce overcommit, you're opening yourself up to periods of instability or no guarantee that workloads will not affect one another.

((number of physical Cores x 1) + (hyper-threaded cores x 0.25) - 1) / vCPUs So on a 12 core/socket system with HT for a XenApp workload with 6 CPUs: ((12 x 1) + (12 x .25) - 1) / 6 = 2 – 3 XenApp hosts per socket at the most

Page 20: Citrix TechXperts Perth May 2016

Summary◦Understand your workloads and usage patterns.◦Apply the appropriate CPU architecture and features:◦NUMA◦COD◦Hyper-threading

Page 21: Citrix TechXperts Perth May 2016

PowerShell Health Check & Documentation Scripts◦Carl Webster’s documentation scripts◦Sacha Thomet’s health check scripts◦My health check scripts

Page 22: Citrix TechXperts Perth May 2016

Carl Webster: http://carlwebster.com

Page 23: Citrix TechXperts Perth May 2016

Sacha Thomet: XenDesktop & XenApp 7.x HealthCheck:http://blog.sachathomet.ch/xendesktop-and-xenapp-7-x-healthcheck-oops-i-did-it-again/

Page 24: Citrix TechXperts Perth May 2016

Sacha Thomet: PVS –le 7.6 HealthCheck:http://blog.appcloud.ch/citrix-pvs-healthcheck/

Page 26: Citrix TechXperts Perth May 2016

Active Directory Health Check & Audit Scripts:http://www.jhouseconsulting.com/

Page 27: Citrix TechXperts Perth May 2016

Questions?