Benchmark Testing
Synthetic Benchmark Testing
SiSoft Sandra 2015 SP2b
The Sandra benchmarks remains a fast and easy way to determine system quality from a CPU and memory subsystem perspective. With the Sandra 2015 suite, the Maximus VIII Impact performed on par with the other Intel Z170-based systems, indicating proper CPU and memory subsystem operation.
Intel Linpack Benchmark v11.3.0.004
The current version of the Intel Linpack benchmark comes with a batch file to run from the command-line interface for running the Linpack tests. It serves as a good indicator of proper system CPU functioning and is considered one of the most intensive CPU benchmarks currently available. This test was repeated three times with the highest repeatable GFlops (Giga-Floating Point Operations Per Second) score recorded.
This CPU torture test is a proven method for identifying possible issues with the CPU to motherboard interface. The Maximus VIII Impact again performs within expectations compared with the other Z170-based systems, further indicating the board's optimal design.
Multimedia and System Benchmark Testing
Maxon Cinebench R15
Maxon’s Cinebench R15 benchmark can be used determine a system's ability to render 3D content based on their Cinema 4D animation software. The CPU benchmark test was run three times, with the highest reproducible Cinebench points score recorded.
The Maximus VIII Impact performed strongly in this multimedia benchmark with its falling in-line with the other Z170-based systems.
FutureMark PCMark 8
FutureMark Corporation’s PCMark 8 can be used to reliably ascertain a system’s performance in a Windows 10-based use environment. The benchmark tests chosen for benchmarking included the Home test, Creative test, Work test, and Applications test in conjunction with Adobe Creative Suite 6.0). All test suites within the PCMark 8 benchmark were run three times, with the highest reproducible PCMark scores recorded.
While its performance lags slightly behind the other test systems in several of the tests, the Maximus VIII Impact's performance still falls within acceptable ranges compared wiht the other Z170-based test systems.
I can’t understand why, in
I can’t understand why, in this day and age, when there still is available place on the back panel, they still cram 4 usb ports in that small of a place.
Doesn’t Z270 come out
Doesn’t Z270 come out tomorrow? 😛
+1
This review is a waste of
+1
This review is a waste of time. Maybe six months ago this board was interesting, but it’s replacement will be out in weeks if not days.
I don’t think motherboard
I don’t think motherboard reviews are ever completely out of date, as motherboards fail a lot more often than CPUs, so someone in the future may be looking for replacement motherboards for their still-working CPU on an older platform. Intel’s lack of progress since sandy bridge also makes staying on the absolute latest platform unnecessary – it’s not a bad idea to buy an older platform in the future if you can find a good deal on it.
You can still buy the Impact
You can still buy the Impact VII.
Your comment is a retread, though.
Any modern motherboard
Any modern motherboard without M.2 is a complete fail.
agreed…. even my Z97
agreed…. even my Z97 Maximus Formula does.
I am also pretty confident the Z170 ASUS Pro Gaming has M.2 as well.
It has m.2, which is
It has m.2, which is populated by the WiFi adapter. That can be removed, or one can get a sled for an m.2 and plug that into the u.2.
Nothing else to add your
Nothing else to add your honor.
This board was aanounced in
This board was aanounced in October 2015 so this review is far too late, unless it was a new board revision or something.
BUT! My next build should be an Maximus IX IMPACT wirh Z270 so glad this board can still show up the world ATX motherboard are so 1995. Time to at least move to microATX.
Morry,
Just an FYI that your
Morry,
Just an FYI that your OC section states you used 4 x 4gb of Corsair RAM.
Ahh, writing reviews from a
Ahh, writing reviews from a template, we see.
Thanks for pointing that out.
Thanks for pointing that out. Fixed…