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 Everest Ultimate, 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.
With the NM10-DTX we did not include some of the more complex testing. We removed the LightWave and Cinebench tests and were forced to remove the 3DMark Vantage test as it reported the 3150 GPU as not having DX10 compatibility. We left in most of the other tests and added a few to get some specific details on how the NM10-DTX performs.
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, Everest and HyperPi 0.99.
Although the numbers here are less than impressive, it is still not all that bad considering the usage model this board and CPU will be put into.
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.
The numbers here tell us the same story that we saw with Sandra.
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 four physical and four logical cores for the i7 and the four physical cores of the i5 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.
Ok, looks like the Atom D510 is not a computational beast. Running the 32M test bogged the system down and caused more than a few problems. Because of this we went with the 16M run for the NM10-DTX. Even with one half the load, the board was pretty slow here. I would say that you are not going to be running any HPC applications on this board. But again, we have to stress that is not what it is intended for.