Our testing methods
There's much to say about the S8 Nitro, but before we move on, let's get our testing methods out on the table, because much of what we're doing from here on out will be affected by our test platform and the like.
As ever, we did our best to deliver clean benchmark numbers. Tests were run at least twice, and the results were averaged.
Our test system was configured like so:
|System||MSI K8T Neo|
|Processor||AMD Athlon 64 3400+ 2.2GHz|
|Chipset drivers||4-in-1 v.4.51|
|Memory size||1GB (2 DIMMs)|
|Memory type||Corsair TwinX XMS3200LL DDR SDRAM at 400MHz|
|Hard drive||Seagate Barracuda V 120GB SATA 150|
|Audio||Creative SoundBlaster Live!|
|OS||Microsoft Windows XP Professional|
|OS updates||Service Pack 1, DirectX 9.0b|
The S3 driver revision we used was version 18.104.22.1682-15.08.09.b. We used ATI's CATALYST 4.2 drivers on the Radeon card and Forceware 56.56 on the GeForce FX 5700 Ultra. One exception: at the request of FutureMark, we used NVIDIA's 52.16 drivers for all 3DMark benchmarking and image quality tests.
The test systems' Windows desktops were set at 1280x1024 in 32-bit color at an 85Hz screen refresh rate. Vertical refresh sync (vsync) was disabled for all tests.
We used the following versions of our test applications:
All the tests and methods we employed are publicly available and reproducible. If you have questions about our methods, hit our forums to talk with us about them.
|An update on Radeon R9 290X variance||25|
|Ubisoft's Snowdrop engine makes The Division look incredible||67|
|No Man's Sky has procedurally generated planets, looks amazing||48|
|Samsung brings 840 EVO to mSATA, drops new firmware for 2.5'' version||12|
|Next Windows release could be more desktop-friendly||148|
|Asus teases custom Radeon R9 290X with DirectCU II cooler||67|
|Report: NSA put agents in World of Warcraft, Second Life||77|
|Bay Trail could power $99 Android tablets||31|
|Rumor: Google cooking up Nexus TV box||41|