With any system you will want to see a combination of synthetic testing and real-world. Synthetics give you a static, easily repeatable testing method that can be compared across multiple platforms. For our synthetic tests we use Sisoft Sandra, Futuremark's 3DMark Vantage and PCMark Vantage, CINEBENCH as well as HyperPi. Each of these covers a different aspect of performance or a different angle of a certain type of performance.
Memory is a big part of current system performance. In most systems slow or flakey memory performance will impact almost every type of application you run.
To test memory we use a combination of Sisoft Sandra and HyperPi 0.99.
Version and / or Patch Used: 2009 SP3c
Developer Homepage: http://www.sisoftware.net
Product Homepage: http://www.sisoftware.net
Buy It Here
Interestingly the synthetic memory performance of the T3eH9 was not as good as we would have thought. This could be related to the issues we had with memory recognition in the BIOS, but is more likely due to tracing and / or skew issues with the BIOS. We are sure that DFI will address this in future BIOS releases.
Version and / or Patch Used: 5.02.1789
Developer Homepage: http://www.lavalys.com
Product Homepage: http://www.lavalys.com
Buy It Here
Everest Ultimate is a suite of tests and utilities that can be used for system diagnostics and testing. For our purposes here we use their memory bandwidth test and see what the theoretical performance is.
Core i5 750 Stock
Core i5 750 @ 4214MHz
Again we see memory performance running a little less than what we would expect of the Core i5 750 on a P55.
Version and / or Patch Used: 0.99
Developer Homepage: http://www.virgilioborges.com.br
Product Homepage: http://www.virgilioborges.com.br
Download It Here
HyperPi is a front end for SuperPi that allows for multiple concurrent instances of SuperPi to be run on each core recognized by the system. It is very dependent on CPU to memory to HDD speed. The faster these components, the faster it is able to figure out the number Pi to the selected length.
For our testing we use the 32M run. This means that each of the cores is trying to calculate the number Pi out to 32 million decimal places. Each "run" is a comparative to ensure accuracy and any stability or performance issues in the loop mentioned above will cause errors in calculation.
With HyperPi we have offsetting results. While at stock speeds the T3eH9 does not perform as well as we would have liked, when we push it the board comes to life and gives us some excellent results for the clock we had.