The SDDCbox Project — Part #3 — Choosing a Mac Pro Configuration

Mac Pro internal view
Mac Pro internal view

In my previous article, “The SDDCbox Project — Part #2 — Testing the Waters“, I exposed my testing strategy which involved testing a few virtual machines on my iMac to get a sense of the type of hardware I will need for my SDDCbox project. The more CPU cores, the more RAM and disk space I’ll be able to afford, the better the chances to get a future proof Mac Pro configuration. Let’s see what Apple has to offer.

Selecting the best Mac Pro configuration

The base Mac Pro configuration comes with 32 GB of RAM (4 × 8 GB R-DIMM) that is running at 2666 MHz and a Xeon W with an 8-core CPU. I would prefer more cores. The next step is to upgrade to a 3.3 GHz version which has 12 cores. With this configuration, as per Apple documentation, the memory clock speed increases to 2933 MHz. I’ll take that even if it enables only a marginal improvement.

Next up, the SSD size. I’m currently using an iMac which comes with a 1 TB SSD drive that is 90% full. On the Mac Pro, I’ll have to upgrade to a 2 TB SSD and it isn’t cheap. As explained in my previous article, virtual machines can consume a lot of space and the best place to run them is on the internal SSD. An external USB-C drive runs slower because the USB channels are not directly tied to the PCIe bus. Internal on-board ports are USB and eSATA capable only which doesn’t help.

What about the upcoming Apple Silicon Macs?

At the WWDC conference last June, Apple officially announced its intention to transition to the ARM architecture, under the name of Apple Silicon, for the Mac product line. It’s a major endeavour for Apple and for the users like me. The question is: should I wait and see what Apple has in store before taking the plunge with an Intel-based Mac Pro? The short answer is no. Here is why.

While it is probably safe to bet on VMware to make a version of Fusion available for the upcoming Apple Silicon Macs, Windows virtualization is probably not coming anytime soon. Windows running inside virtual machines on ARM is not possible right now and no plan was announced. It is a dealbreaker for me as I need Windows Servers in my SDDC environment for services like Active Directory.

The Mac Pro will probably be the last machine to transition to the ARM architecture. Why? For many reasons. First, many professional users rely on applications currently not optimized for ARM processors. These applications are not going to be the first to be optimized unless there is a clear performance advantage, something that is unproven at this time for high-end machines like the Mac Pro. Second, the Mac Pro is a low-volume product. Apple will go after higher volume products first like the MacBook line, which will benefit from Apple Silicon. Four, many drivers will need to be upgraded to support the new architecture on which many pieces of equipment are based-on to operate. Lastly, the Mac Pro just came out in 2019, and there is still a lot of potential in it.

All this being said, I’m not playing fool. Sure, I’ll wait for November Apple Event as Apple could make some changes to their current Mac Pro offerings and pricing.

The verdict is…

Unless there are surprises, my configuration choice goes to the 12 cores CPU, 32 GB of RAM and 2 TB SSD. Additional RAM will be upgrade to 192 GB by the replacement of the 4 × 8 GB R-RIMMS with a third-party RAM manufacturer with 6 × 32 GB R-DIMMS. As for the graphic card, even going with the base configuration, it will be an upgrade from the one in my 2017 iMac.

Depending on the timing, this Mac Pro will probably come with macOS Big Sur. A careful check on VMware Fusion’s blog announcing Fusion 12, confirms that everything is fine. Fusion does support Apple’s latest OS and the list of known issues is quite short and doesn’t contain any showstoppers.

In my next article in this series, I’ll explore the upgrade path strategies to go from an iMac to a Mac Pro.

One thought on “The SDDCbox Project — Part #3 — Choosing a Mac Pro Configuration

Add yours

Leave a Reply

Up ↑

%d bloggers like this: