You shouldn't regard this as a cpu benchmark, for several reasons, including the following:
Well I agree with you partially.
1. I will try to implement the data prefeching element to the benchmark, so it will actually make a use out of the CPU cache. Right now I know that the benchmark is not using the cache very efficiently. In fact I think it is not using the cache at all.
Once again data prefech is more effective on G4 and Athlon and less effective on Pentium 4 therefore the next revision will give all of the platforms an opportunity to show their architectural strength rather than just the Mhz strength.
2. I am compiling this program on a g++ compliant, generic, freeware Dev C++ compiler, on Windows. Therefore I don't think that it will optimize the code better than generic gcc or g++. I would say all of them will compile the code in a similar way because they come from one gcc source. I am not using anything special, such us MS Visual C++. Just generic, similar, plain vanilla compilers.
3. If you will look at the results....Well, they seem to depend primely on the CPU speed and not on the memory speed,
therefore how you can say it is not a cpu benchmark?
The CPU speed seems to be a critical factor here...
Take a look. Similar platforms, but diffrient results:
56.63 seconds on:
P4 2.0Ghz OCed to 3.2Ghz
Albatron PEV PRo
512MB Samsung True PC3200 @ 2.66 Multiplier (DDR 425)
and
P4 1.6A@2.4Ghz
Albatron PX845PEV Pro
512MB DDR400
Win Xp Pro
76.281 seconds
In both cases, the memory speed is similar, yet the difference between CPUs used is 800 Mhz.
Therefore I would argue that for some odd reason SortMark likes fast CPUs? :Q
