Cinebench 2003 & 3DMark05: CPU
The Cinebench 2003 benchmark is an OpenGL 3D rendering performance test, based on the commercially available Cinema 4D tool suite. This is a multi-threaded, multi-processor aware benchmark that renders a single 3D scene and tracks the length of the entire process. The time it took each test system to render the entire scene is represented in the graph below (listed in seconds).
We should note that because the host processor we ran for all of the motherboards in this test was a single-core Athlon 64 FX-53, the only option available was to test in Cinebench's single CPU thread mode. Multi-core processor performance, as one would see with an Athlon 64 FX X2, for example, would undoubtedly be faster.
Once again, whether we consider the single-chip implementation of the nForce 4 SLI or the two-chip nForce 4 SLI X16 with its additional 16 lanes of PCI Express on board, processing throughput from either solution is virtually identical.
3DMark05's built-in CPU test is a DirectX game engine performance metric that's useful for comparing relative performance between similarly equipped systems. This test consists of two different 3D scenes that are generated with a software renderer, which is dependant on the host CPU's performance. This means that the calculations normally reserved for your 3D accelerator are instead sent to the central host processor. The number of frames generated per second in each test are used to determine the final score based on a weighted average.
With 3DMark05's CPU test, the ASUS A8N32 SLI Deluxe took the lead position by a more comfortable margin. It's important to note that this was achieved with a single GeForce 6800 GT installed, so the board's additional X16 graphics slot isn't affecting the results in any way. What we're looking at here is a 5% differential from the fastest score turned out by the A8N32 SLI Deluxe and the slowest score offered by the A8N SLI Deluxe. Amongst the three nForce 4 SLI classic boards it's a virtual dead heat, but the A8N32 SLI Deluxe seems to have slightly better overall bandwidth in this test that mainly highlights CPU polygon throughput.