Our testing methods
All tests were run three times, and their results were averaged, using the following test systems.
|Processor||AMD Opteron 246 2.0GHz (1 processor)|
|Front-side bus||HT 16-bit/800MHz downstream|
HT 16-bit/800MHz upstream
|Motherboard||Tyan Thunder K8W|
|North bridge||AMD-8151 AGP tunnel|
AMD-8131 PCI-X tunnel
|South bridge||AMD-8111 I/O hub|
|Chipset drivers||AMD chipset driver pack 2.10|
|Memory size||1GB (2 DIMMs)|
|Memory type||Corsair CM72SD512RLP-3200/S Registered PC3200 DDR SDRAM|
|Graphics||NVIDIA GeForce FX 5200|
|Graphics driver||ForceWare 61.76|
SIIG Serial ATA PCI
Silicon Image 126.96.36.199
Maxtor Atlas 15K 73GB
Western Digital Raptor WD360GD 37GB
|Operating System||Windows XP Professional SP2 with DirectX 9.0c|
The Serial ATA and SCSI cards were used in different PCI-X slots on different PCI-X busses. Each card had an entire PCI-X bus to itself, so bandwidth sharing won't be an issue.
We used the following versions of our test applications:
The test systems' Windows desktop was set at 1280x1024 in 32-bit color at a 75Hz screen refresh rate. Vertical refresh sync (vsync) was disabled for all tests. All of the 3D gaming tests used the high detail image quality settings.
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.
|The TR Podcast 179: Radeon R9 Fury X tested & dissected||3|
|F1 2015 revs up with new teaser trailer||8|
|Fractal Design's Define S case reviewed||13|
|Microsoft adds $1,299 Core i7 version to Surface Pro 3 lineup||40|
|Nvidia's 353.38 hotfix driver fixes Chrome crashes, G-Sync lag||27|
|Samsung and LG show off battery technology improvements||19|
|Arkham Knight gets first patch, improvement plans||52|
|Samsung will patch its software to restore Windows Update settings||43|
|OnePlus will launch its new phone in virtual reality||19|