When planning a Lync deployment, we are finding some customers are running into issues in planning the CPU overhead of their systems. For many people, they are using the “Lync Server 2010 Capacity Calculator” to generate their anticipated system load.
Lync Server 2010 Capacity Calculator
The only problem with this tool is that unlike the Exchange role calculator, which defines the end state megacycle requirement, the Lync calculator projects it’s end state CPU load based on a dual processor, quad-core, with a 2.33 GHz system (18,664 megacycles). To correct this, the true benchmark settings of the end state core processor should be factored. For virtual machines within VMware this is simple, as you can use a Vsphere client to locate the CPU core statistics for your ESX host. Otherwise you can use the site below to obtain the rated per-core megacycle per processor; and thus the total megacycles per server.
To learn more on Virualization, please visit our Website.
More in depth hardware considerations can be found at the TechNet article: "Scenario-Based Capacity Planning"
For more information, contact us at info@rutter-net.com
Comments