An important point to realize with the major motherboard manufacturers is that the motherboard server team is a wholly different business unit to the end-user motherboard team. As a result, the only overlap between these two departments (apart from purchasing hardware) is at high level management. This usually means that the design teams do not talk to each other, the development teams do not talk to each other, and the BIOS/software teams are separate. This is a bit of a shame to be honest, because while the end-user side of the company is focused on delivering a good user experience, it does not translate over to the server side of the company which is more focused on robustness and support. This means that our BIOS interface, while technically an EFI/UEFI construct, is a simple text and select affair.

The front screen contains information on the BIOS version, the CPUs installed and the memory installed, but fails to mention which motherboard is in use. With standard graphical interfaces, even if they came to server implementations, would benefit from fan speeds and CPU temperatures on this screen as well.

The Advanced menu contains most of the motherboard options, especially the CPU configuration and the fan controls.

The fan controls are dire – for six fan headers, there is only one option and the rate of increase of fan speed is determined by a single value. For a workstation oriented motherboard, I would have assumed that an adaptive system would need to be in place.

The option for Above 4G Decoding, required for certain PCIe co-processors, is found in the PCI Subsystem menu and is disabled by default.

Users who are interested in every morsel of performance should head over to the CPU Power Management menu where the Energy Performance option should be changed to full performance. This makes the turbo modes more aggressive, maintaining a higher turbo on the CPUs for longer.  We ran our system at the stock default option - balanced performance.

The GA-7PESH3 does support Hot Plug on the SATA ports, but this is disabled by default. This makes more sense if this motherboard is placed in a case with hot-plug bays rather than RAID applications.

Memory control is limited, with the Chipset -> North Bridge menu offering most of the options. The user can select the DDR3 Speed here, although sub-timing control is not offered. There is a DIMM information screen so diagnosis of an errant memory module can take place:

VT-d is also present, and in our configuration was enabled by default. There was no direction mention of VT-x in the BIOS.

The rest of the BIOS supports data logging for the management interface as well as boot order, fast boot options for Windows 8 and boot override functionality.


For the reasons mentioned at the start of the BIOS analysis, the software system is similarly different to the channel motherboard market. There is no software directly usable or downloadable from the product page, and thus the management interface becomes the sole ‘software’ available for use.

The system uses a MergePoint EMS interface, similar what we saw on the GIGABYTE GA-7PESH1. After a login (default settings are admin/password) the above screen is shown, and if I were a server admin I would have like to see some indication of what hardware installed in the system on the front page, and if the machine is switched on and running, if one of a list of operating systems are detected.

As with these management systems, security is a major priority, and this system gives a level of IP blocking rather than an IP whitelist:

This is combined with a list of enabled users who have access:

The system can also adjust its web server management settings for the interface, giving timeouts and port selection.

The management system is based on a Linux kernel, as shown in the LDAP Configuration Page, which can also be updated akin to a firmware update:

One of the more important uses for the management software is remote control of the system. This comes in two parts – direct control over the state (on/off) of the system and the interface to the video output. The former is located in Power -> Control:

With the direct OS control provided by a virtual KVM over a Java based implementation:

Another aspect of the management center is keeping track of voltages, fan speeds and temperatures and indicating when they are out of the normal working window.

The GA-7PESH3 uses fourteen different temperature sensors for this, each of them with limits defined in firmware. I’m sure that a custom system would prefer these to be manually adjustable.

The management engine also keeps track of the system event log, for when the machine is booted or one of the aforementioned sensors goes out of optimal functioning parameters. When the temperature gets too high, or a fan fails, the system can react by forcing a reboot, power cycle or power the system down:

GIGABYTE Server GA-7PESH3 Motherboard Review: 2P or not 2P 2014 Test Setup and System Benchmarks


View All Comments

  • tuxRoller - Saturday, September 6, 2014 - link

    I found a reference on serverfault that says windows ultimate 7 supports up to two sockets. How well it is supported is another matter...than anandtech seems uninterested in investigating. Reply
  • Kevin G - Sunday, September 7, 2014 - link

    The scheduler is the same between Windows 7 Pro and Windows 2008R2. The difference is in the configuration defaults.

    The more defining factor between a single and dual socket system in Windows is how it handles NUMA. Modern chips all have their own memory controller and things get complicated when a thread running on one processor requests data off the memory in another socket. That'll cause a slow down due to the additional latencies involved. Ideally the scheduler will run a thread on the same socket as the memory it accesses but for large data sets, this isn't possible or practical to continually context switch were a thread runs. This is why having a system with the same clock speed, the same number of cores and the same amount of memory will generally be faster on a single socket than a dual.
  • Filiprino - Sunday, September 7, 2014 - link

    What about pinning a game to a socket?
    You should get the same performance as the equivalent single socket CPU, same frequency.
  • Gonemad - Monday, September 8, 2014 - link

    I believe the point of the reviewer was to prove this motherboard is worthless to gaming enthusiasts, that will get better bang for buck elsewhere.

    It could be a tremendous gaming platform back in the single-core day, as it was the case. I knew a couple of people that built gaming machines out of server parts exactly to get the benefits of a dual-core system, even when the applications were not built for it, but just forcing Windows to run on the 2nd chip, while the game would run on the 1st. At least, that was the consensus back then, however wrong that may be.

    Today, it is proved to be a moot point, since you get more performance out of a single 8-core chip, with shared cache and optmizations, than relying on true dual-chip design to get your cores.
    Applications that already relied on multiple cores just took a leap ahead, having so many of them to populate, which was evident on the compression software's benchs.

    I believe that this whole benchmark is far from useless; it proves that this use case is totally incorrect for the purpose of gaming. On the other hand, the server platform is an excellent number cruncher, with the reliability to match it, but it can take some gaming on the side dish without effort. It won't take 'best bang for buck' lists by storm, but it won't force the buyer to build a machine just for gaming.
  • Arms9ForSoul - Tuesday, May 10, 2016 - link

    As ohm's law becomes stagnant, and manufacturing size become's limited, it'd be nice to be able to buy a mainstream/performance mobo with multiple CPU sockets. This would also be an easy way to sell APU's since it would be cheaper and have "better" performance. Reply

Log in

Don't have an account? Sign up now