Single page Print

Our testing methods
Most of the numbers you'll see on the following pages were captured with PresentMon, a software utility that uses data from the Event Timers for Windows API to tell us when critical events happen in the graphics pipeline. Namely, we're interested in the time between present() calls, which correlate with the frame times that we used to collect using Fraps.

As ever, we did our best to deliver clean benchmark numbers. Our test systems were configured like so:

Processor Core i7-7700K
Motherboard Gigabyte Aorus GA-Z270X-Gaming 8
Chipset Intel Z270
Memory size 16GB (2 DIMMs)
Memory type G.Skill Trident Z
Memory timings 18-19-19-39 2T
Hard drive 2x Kingston HyperX 480GB
Corsair Neutron XT 480GB
Power supply Corsair RMx 850W
OS Windows 10 Pro


  Driver revision GPU base
core clock
GPU boost
Radeon R9 Fury X Radeon Software 17.2.1 --- 1050 1000 4096
EVGA GeForce GTX 1070 SC2 GeForce 378.78 1594 1784 2002 4096
GeForce GTX 1080 Founders Edition 1607 1733 2500 8192
GeForce GTX 1080 Ti Founders Edition 1480 1582 1753 11264

Thanks to Intel, Corsair, Kingston, and Gigabyte for helping to outfit our test rigs with some of the finest hardware available. AMD, Nvidia, and EVGA supplied the graphics cards for testing, as well.

Some game settings (especially texture sizes) were not friendly to the Radeon R9 Fury X's 4GB of RAM. Where necessary, we reduced these settings to prevent crippling performance issues. All other in-game settings remained the same between the Fury X and the Nvidia cards on the bench.

Unless otherwise specified, image quality settings for the graphics cards were left at the control panel defaults. Vertical refresh sync (vsync) was disabled for all tests. We tested each graphics card at a resolution of 3840x2160 and 60 Hz, unless otherwise noted.

The tests and methods we employ are generally publicly available and reproducible. If you have questions about our methods, hit our forums to talk with us about them.