On Fri, Apr 24, 2009 at 01:52, Łukasz Lew lukasz@gmail.com wrote:
I get
g++-4.1 35 kpps/GHz
g++-4.2 45 kpps/GHz
g++-4.3 40 kpps/GHz
I'm happy it's quite consistent on core2
I'm curious about 4.4 as well.
g++-4.4 45 kpps/GHz
package gcc-snapshot on ubuntu
$
According to my math, that comes out to around 205 cycles per playout move.
Pretty damn good, I'd say.
Łukasz Lew wrote:
On Fri, Apr 24, 2009 at 01:52, Łukasz Lew lukasz@gmail.com wrote:
I get
g++-4.1 35 kpps/GHz
g++-4.2 45 kpps/GHz
g++-4.3 40 kpps/GHz
I'm happy it's quite consistent
My math seems to be way different
1e9 / 45000= 22,222 cycles per playout
On Apr 24, 2009, at 12:22 PM, Michael Williams michaelwilliam...@gmail.com
wrote:
According to my math, that comes out to around 205 cycles per
playout move. Pretty damn good, I'd say.
Łukasz Lew wrote:
On Fri,
Of course, I now realize what I missed after sending it. Playout vs.
Playout move... At a little over 100 moves per playout, our numbers
agree
Sent from my iPhone
On Apr 24, 2009, at 12:54 PM, Jason House
jason.james.ho...@gmail.com wrote:
My math seems to be way different
1e9 / 45000=
You have to take into account that there is time needed to load base
position and score the game after playout.
I remember that in my old tests it was around 180 cc per move.
(libego got a little bit faster since then)
Lukasz
On Fri, Apr 24, 2009 at 18:56, Jason House jason.james.ho...@gmail.com
