Asus P5AD2-E i925XE Motherboard

Article Index

Cinebench and Kribibench

 

The Cinebench 2003 benchmark is an OpenGL 3D rendering performance test, based on the commercially available Cinema 4D application.  This is a multithreaded, multiprocessor 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 ran two sets of numbers, one in single-thread mode, and another in the benchmark's multithread mode for our Hyper-Threading-enabled P4 test systems.  The Athlons are only capable of running the single thread test.

Cinebench 2003 Performance Tests
3D Modeling & Rendering Tests

In our Cinebench test the Athlon 64 4000+ system faired much better versus the P4s and with the Asus P5AD2-E motherboard.  In addition, the Asus P5AD2-E proved itself just a hair quicker at rendering the test Cinema 4D scene in this benchmark.  Finally, utilizing Intel's Hyperthreading in conjunction with the Asus motherboard, afforded us sizable gains in performance, with all the P4 systems processing two threads of the rendering workload simultaneously.

Kribibench v1.1
Details: www.adeptdevelopment.com

Next up, we used the KribiBench benchmark produced by Adept Development.  KribiBench is an SSE aware software renderer.  A 3D model is rendered and animated by the host CPU, and the average frames per second are reported.  We used two of the included models with this benchmark: the "Sponge Exploded" model consistenting of 19.2 million polygons and the ever massive "Ultra" model consisting of 16 billion polygons.

 

Here, as the old saying goes "cache is king" and the P4 EE infused setup with the Asus P5AD2-E scores top honors again.  In this test as well, the Asus i925XE motherboard, shows it's right up to par and maybe a bit more versus our Intel branded i925XE reference system.

Tags:  Asus, Motherboard, board, AR

Related content

Comments

Show comments blog comments powered by Disqus