ScienceMark 2.0 FINAL 32 - Bit version 21032005

Changelog between 07FEB05 -> 21MAR05

-64-bit support for Windows x64 edition
--------------------------------------------
Important notes for 64-bit support.
: 64-bit is a beta version at the moment.
: Performance may change in the future depending on how we tune for fp performance. You should see significant speedups on both EM64T and AMD64 processors in 64-bit mode. Part of this is due to compiler improvements. : Intel EM64T systems are supported, however, ScienceMark2 won't be able to detect them properly in MemBench.
This will be remedied in a future version.
: CipherBench is not supported in 64-bit mode. Running AES returns an incorrect result, that is impossibly too fast.
This will be remedied in a future version.
: Both SGEMM and DGEMM benchmarks are restricted to compiler only under 64-bit edition.
This will be remedied in a future version.
: There are several new memory cores that are present in the 64-bit build of Membench that are not present in 32-bit edition.
This is due to the new ISA.
: STREAM is tweaked a bit
--------------------------------------------

-Fixed a rare crash that would occur immediately upon startup.
-Sciencemark2 can now be run from the command line!
Command line options:

-automate : Run through each benchmark without user interaction. Upon completion, ScienceMark2 will automatically close.
-cipherbench : Run through the cipher benchmark
-dgemm : Run through the dgemm benchmark using the compiler core
-dgemm:compiler : Run through the dgemm benchmark using the compiler core
-dgemm:sse2s : Run through the dgemm benchmark using the scalar sse2 core
-dgemm:sse2v : Run through the dgemm benchmark using the vector sse2 core
-dgemm:x87 : Run through the dgemm benchmark using the x87 core
-help : Display all command line options
-membench : Run through the memory benchmark
-moldyn : Run through the molecular dynamics benchmark
-moldyn:file.in : Run through a custom simulation using file.in
-primordia : Run through the primordia benchmark
-primordia:file.in: Run through the primordia benchmark using the custom file provided.
-runallbench : Run through the entire benchmark. -automate is implied.
-sgemm : Run through the sgemm benchmark using the compiler core
-sgemm:compiler : Run through the sgemm benchmark using the compiler core
-sgemm:sse : Run through the sgemm benchmark using the sse core
-sgemm:3dnow : Run through the sgemm benchmark using the 3dNow! core

Note that ScienceMark2 in 64-bit edition does not support sgemm:sse, sgemm:3dnow, dgemm:sse2s, dgemm:sse2v, or dgemm:x87.
To run a fully automated benchmark of everything, try:
sciencemark2 -automate -runallbench

- Changed the behavior of the "Run All Benchmarks" function. Sciencemark will no longer run through the entire collection of primordia and molecular dynamics files, but will run through primordia simulation of silver, and molecular dynamics simulation of helium and argon. (these are the default benchmarks that everyone is used to)
- Sciencemark2 calculates a composite score if all benchmarks are run from in the Run all benchmarks mode.
- Sciencemark2 can compare your score with other scores you have generated, or from other people.
For instance, a score of 1000 in an area means your system is comparable to a dual Opteron 246 (2.0 Ghz) with 4 GB registered PC2700 RAM, on a non-NUMA motherboard.

Features 

Science Mark 2.0 is an attempt to put the truth behind benchmarking. In an attempt to model real world demands and performance, SM2 is a suite of high-performance benchmarks that realistically stress system performance without architectural bias. 
The benchmarks in wide use today fail to accurately reflect system performance due to the following:

1. Relevance: The benchmarks test only 1 application and don't address a wider array of applications more representative of the user's market.
2. Abstraction: They are entirely comprised of synthetic tasks that don't perform a complex meaningful task.
3. Quality: May be poorly constructed from a C or Fortran perspective and limited in their ability to measure the true potential of a system.
4. Objectivity: The test is developed on or tuned for one architecture resulting in implicit performance bias. 

Synthetic benchmarks are useful, and can tell the user valuable performance characteristics about their system's performance, but they should not be used in entirety to measure system performance; this role is reserved in greater part to real applications performing real tasks. Science Mark 2.0 is comprised of 7 benchmarks, each of which measures a different aspect of real world system performance.