it's pretty fast, fast enough for benching *and! comparing.
it doesnt have to be the *fastest.
it's precise, uses CRC and the HW based clock (not winclock) and provides one result (k/sec.)
witch is very easy to compare. it does not need *any additional librarys / installation.
I know him, he specially choosed the gauss algo. because of
its high *and continues (no fluctuation) cpu load.
there are no optimizations for any cpu-manufacturer on board.
all of them will benched with the same non-optimized code.
As he said, this will show the real world, better.
he also has an *incredible fast chudnovsky
algorithm (incl. binary splitting), but this one will not produce
that clean load on the cpu/memory as the gauss do.
You can see that via performance monitoring Unit (PMU-CPU).
so i don't think he will include this into maxxpi.
His MaxxPI² is very professional,
i was one of the first beta-testers on board.
is there an difference between dual/tripple channel on x58?
search the web, you will find nothing. try maxxpi2 and you will see it
(memory <> overall-memory)
this is also very interesting:
and viewing/exporting own results (excel):