Our testing methods
As ever, we did our best to deliver clean benchmark numbers. Tests were run at least twice, and the results were averaged.

For the test, our SS50 and the comparison systems were configured as follows:

Soyo KT333 DRAGON Ultra

Shuttle SS40G
w/onboard video

Shuttle SS40G
w/PCI video

Processor

AMD Athlon XP 2000+ 1.67GHz

Front-side bus

266MHz (133MHz double-pumped)

BIOS revision

K7VXB_2AP1R

FS40S025

Chipset

VIA KT333

SiS 740

North bridge

VT8367

SiS 740

South bridge

VT8233A

SiS 961

Chipset drivers

VIA 4-in-1 4.38(2)v(a)

AGP Driver 1.09

Memory size

512MB (1 DIMM)

Memory type

Corsair XMS3000 DDR SDRAM CAS 2

Graphics

NVIDIA GeForce 3 Ti 500 64MB
(Detonator XP 28.32 video drivers)

SiS VGA driver 2.05SS

NVIDIA GeForce 4 MX420 PCI 64MB
(Detonator XP 28.32 video drivers)

Sound

C-Media 8738

Storage

Maxtor DiamondMax Plus D740X 7200RPM ATA/100 hard drive

OS

Microsoft Windows XP Professional

OS updates

None

Like the SS50, the SS40G's integrated graphics use a portion of main system memory for a frame buffer, which will likely have a detrimental effect on the memory bandwidth of the system. As a point of comparison, we tested the SS40G both with the on-board integrated graphics and with a PCI GeForce 4 MX420 card, the fastest available PCI video card. For the configuration that used the integrated graphics, we gave the SS40G 64MB of graphics memory, leaving 448MB for system memory.

For those who might be considering the option of using the SS40G as their main computer, we decided to test it against a more "mainstream" system assembled out of parts with a similar price point. Thus we chose the Soyo DRAGON Ultra board; the SS40G and the Soyo trade back and forth on some features (the SS40G has Firewire, while the DRAGON Ultra has USB 2.0, for example) but are conceptually fairly close, incorporating a relatively large number of features on-board.

The test systems' Windows desktops were set at 1024x768 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.