System Performance

Not all motherboards are created equal. On the face of it, they should all perform the same and differ only in the functionality they provide - however, this is not the case. The obvious pointers are power consumption, but also the ability for the manufacturer to optimize USB speed, audio quality (based on audio codec), POST time and latency. This can come down to the manufacturing process and prowess, so these are tested.

For this review we are running using Windows 10 64-bit with the 1909 update as per our Ryzen Threadripper 3960X and 3970X CPU review.

Power Consumption

Power consumption was tested on the system while in a single ASUS GTX 980 GPU configuration with a wall meter connected to the Thermaltake 1200W power supply. This power supply has ~75% efficiency > 50W, and 90%+ efficiency at 250W, suitable for both idle and multi-GPU loading. This method of power reading allows us to compare the power management of the UEFI and the board to supply components with power under load, and includes typical PSU losses due to efficiency. These are the real-world values that consumers may expect from a typical system (minus the monitor) using this motherboard.

While this method for power measurement may not be ideal, and you feel these numbers are not representative due to the high wattage power supply being used (we use the same PSU to remain consistent over a series of reviews, and the fact that some boards on our testbed get tested with three or four high powered GPUs), the important point to take away is the relationship between the numbers. These boards are all under the same conditions, and thus the differences between them should be easy to spot.

Power Long Idle (w/GTX 1080)Power OS Idle (w/GTX 1080)Power Prime95 Blend (w/GTX 1080)

Looking at the power consumption performance of the GIGABYTE MZ31-AR0 motherboard when tested with our AMD EPYC 7351P processor, the figures we got are in line with what's expected. In contrast to the AMD Ryzen Threadripper 1950X and 2950X, these both have a TDP of 180 W, while the EPYC 7351P has a TDP of between 155 and 170 W. This shows in our tests under load when pitting the SP3 boards up against the X399 models. 

Non-UEFI POST Time

Different motherboards have different POST sequences before an operating system is initialized. A lot of this is dependent on the board itself, and POST boot time is determined by the controllers on board (and the sequence of how those extras are organized). As part of our testing, we look at the POST Boot Time using a stopwatch. This is the time from pressing the ON button on the computer to when Windows starts loading. (We discount Windows loading as it is highly variable given Windows specific features.)

Non UEFI POST Time

It's no secret that professional-based motherboards have longer POST times than desktop models, and our results are a perfect example. The GIGABYTE MZ31-AR0 has a default POST time of just over 71 seconds, which is due to the controller and BMC initialization, which does take longer than other controllers to prepare. With networking and other non-essential controllers disabled, we managed to get the POST time down to a more modest 62.2 seconds.

DPC Latency

Deferred Procedure Call latency is a way in which Windows handles interrupt servicing. In order to wait for a processor to acknowledge the request, the system will queue all interrupt requests by priority. Critical interrupts will be handled as soon as possible, whereas lesser priority requests such as audio will be further down the line. If the audio device requires data, it will have to wait until the request is processed before the buffer is filled.

If the device drivers of higher priority components in a system are poorly implemented, this can cause delays in request scheduling and process time. This can lead to an empty audio buffer and characteristic audible pauses, pops and clicks. The DPC latency checker measures how much time is taken processing DPCs from driver invocation. The lower the value will result in better audio transfer at smaller buffer sizes. Results are measured in microseconds.

Deferred Procedure Call Latency

We test the DPC latency at default settings from out of the box, and the GIGABYTE board performs well against other models on test.

Board Features, Test Bed and Setup CPU Performance, Short Form
Comments Locked

37 Comments

View All Comments

  • xyvyx2 - Wednesday, March 25, 2020 - link

    physically the same, but not compatible :(
    https://en.wikipedia.org/wiki/Socket_sTRX4
  • Operandi - Wednesday, March 25, 2020 - link

    Looks like the perfect board for my home Pfsense build. In all seriousness though looks like a pretty baller single socket Epyc board if only I had something lined up that could use it.
  • Deicidium369 - Sunday, April 12, 2020 - link

    a door stop would be an appropriate use for it - unlikely AMD would have the drivers ironed out.
  • MenhirMike - Wednesday, March 25, 2020 - link

    Does anyone know if it's possible to use Unbuffered ECC RAM with EPYC? Thinking of upgrading from a Threadripper to an EPYC for a Server, but I don't want to rebuy RAM as I already got enough DDR4 ECC UDIMMs.
  • Slash3 - Wednesday, March 25, 2020 - link

    Some Tyan boards seemingly support it from their spec sheets, but it's something that most reviews don't cover, unfortunately.

    Patrick at Serve the Home has also mentioned support on some older boards, but unfortunately he didn't mention any specific models in the one comment I was able to dig up on their forums.
  • MenhirMike - Wednesday, March 25, 2020 - link

    Also, curious if the board supports bifurcation - the lack of M.2 Slots would make it perfect for e.g., an ASUS HYPER M.2 X16 or Supermicro AOC-SLG3-2M2 card, but for that it needs to support bifurcation of an x16 into 4x4 or an x8 into 2x4 slots.
  • Slash3 - Wednesday, March 25, 2020 - link

    The Hyper M.2 is long enough that you wouldn't be able to insert the card into the first five slots, which is a bit of a bummer. I can't confirm bifurcation support but I'd be very surprised if it didn't have it.
  • phoenix_rizzen - Thursday, March 26, 2020 - link

    We built our first iSCSI storage box around this motherboard. Have nothing but great experiences with it, and the IPMI implementation is light-years beyond what Supermicro supports (the GB IPMI is fully-web-enabled, using HTML5 KVM/console redirection, compared to the horrid Java implementation that Supermicro uses).

    The only downside if the SlimSAS connectors. It's very easy to find SlimSAS-to-SATA connectors (even comes with some in the box). Pain in the ass to find SlimSAS-to-SFF8084 connectors to connect to multi-lane, direct-attach backplanes! They exist, but nobody actually carries them (at least nobody that we could find in North America). Had to get them from a cable maker in China, which took the very slow boat to arrive.

    For our first build, I messed up the model number for the backplane, ending up with an SAS expander version, so we had to use an HBA anyway.

    For our second iSCSI storage server, we switched to the MZ01-CE0 motherboard. This includes 10GBase-T ports instead of SFP+. Other than that, it's virtually the same board. Got the right model backplane, and the SlimSAS-to-SFF8084 cables, giving 16 SATA connections direct off the motherboard.

    For our next ZFS storage server, we'll be using MZ01-CE0 in a 2U chassis, running the OS off the motherboard connectors, with LSI/Broadcom/whoever-they-are-now HBAs with external connectors going to multiple 45-bay storage chasssis. That setup works great with all the extra PCIe lanes. :)
  • fazalmajid - Friday, March 27, 2020 - link

    What OS do you use for your ZFS/iSCSI servers?
  • phoenix_rizzen - Saturday, March 28, 2020 - link

    FreeBSD

Log in

Don't have an account? Sign up now