Since the release to manufacturing (RTM) of Exchange 2013, you have been waiting for our sizing and capacity planning guidance. This is the first official release of our guidance in this area, and ...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi,
Thanks for this long waited sizing information :)
Juste a typo in the Transport storage requirements, it is not Per-server transport DB size = 102 GB but 102 MB :p
And an another in Processor requirements, for the E5-2630 processor "Result = 430" - "Baseline = 414" - Core = 12, so per-core SPECint_rate2006 score = 430 / 12 = 35,8333 and Per-core SPECint_rate2006 Baseline score = 414 / 12 = 34,5.
At the end estimated available Exchange workload megacycles = (35,8333 x 2000) / (34,5) = 2077,2928 MHz
(correct me if I am wrong)
I have one question : In the Total memory required per-server for the CAS additionnal memory needed, in the formula you use "mbx mcycles per-user" with the value 8.50, if I do not make mistake the value is from "Mcycles per User, Active DB Copy or Standalone (MBX only)" for 200 messages per user per day.
Why do you use this value stated "MBX only" in the table ? (is the column is in fact for "CAS only" ?)
Regards,
Anthony COSTESEQUE