hi all,
today, i will introduce my benchmark,
that i develop since 2006 - until now...
it started with this version in 2006-2007 (developing stopped):
and ended with that ( MaxxPI² - Introducing ) , showing here memory benchs:
for now, it's an closed beta, but if you want you can test MaxxPi-PreView,
it contains the PI-Engine of MaxxPi², so the reaced results are exactly the same:
here some screen's from MaxxPi-PreView:
features:
MMX / SSE Support
hardware based time measurement to, approx. 1-2ms exactly
arithmetic-deep: 128 m max.
memory usage approx. 1.2gb ram (with 128M)
multithread (not multicore, MaxxPi² will do multicore, not the preview)
description of score: K / sec.:
is given to compare easier achieved results,
so instead of having to say 2min 32sec 343ms...
now you need only to tell on single number, k/sec.
it is nothing else than:
the number of calculated decimal places per sec. in K (1024)
for example:
1m became 356.2 (K/sec.) means that the cpu was able to
calculate 364,748.8 (1024 x 356.2) decimal places per sec.
further informations:
download: MaxxPI² - Introducing (zip file, about 500kbyte, no install)
if anybody will take part (closed beta) please contact me via PM.
tell me about your used HW, and your preferred nick and email-adress.
regards
alice
today, i will introduce my benchmark,
that i develop since 2006 - until now...
it started with this version in 2006-2007 (developing stopped):
and ended with that ( MaxxPI² - Introducing ) , showing here memory benchs:
for now, it's an closed beta, but if you want you can test MaxxPi-PreView,
it contains the PI-Engine of MaxxPi², so the reaced results are exactly the same:
here some screen's from MaxxPi-PreView:
features:
MMX / SSE Support
hardware based time measurement to, approx. 1-2ms exactly
arithmetic-deep: 128 m max.
memory usage approx. 1.2gb ram (with 128M)
multithread (not multicore, MaxxPi² will do multicore, not the preview)
description of score: K / sec.:
is given to compare easier achieved results,
so instead of having to say 2min 32sec 343ms...
now you need only to tell on single number, k/sec.
it is nothing else than:
the number of calculated decimal places per sec. in K (1024)
for example:
1m became 356.2 (K/sec.) means that the cpu was able to
calculate 364,748.8 (1024 x 356.2) decimal places per sec.
further informations:
download: MaxxPI² - Introducing (zip file, about 500kbyte, no install)
if anybody will take part (closed beta) please contact me via PM.
tell me about your used HW, and your preferred nick and email-adress.
regards
alice
Comment