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.
|Wait, we're giving away $1500 in PC hardware?||4|
|Nvidia GeForce 337.61 beta hotfix display driver released||1|
|AMD earnings previewed||6|
|Ars Technica reviews Windows Phone 8.1||11|
|Steam usage patterns reveal shameful number of unplayed games||49|
|Google buys Titan Aerospace||11|
|What's next after Google Glass? Try Google contact lenses||8|
|Major smartphone makers to integrate kill switches into future mobile devices||20|