I don't know, what language are you using? Did you do any optimizations? How many clock cycles does it take your program on average to make and undo a move (just counting the core board update)?
BTW you didn't specify board size and hardware, so I assumed 19x19 and a modern PC. Erik On Thu, Oct 15, 2015 at 12:56 AM, Gonçalo Mendes Ferreira <go...@sapo.pt> wrote: > Really? I didn't mention it but it's uses MCTS-UCT with RAVE, progressive > pruning, mercy thresholds and max playout depth, etc. What could I be > missing that is that much of a boost in the playouts, in your experience? > > Gonçalo > > > On 14/10/2015 23:40, Erik van der Werf wrote: >> >> You should be able to do at least 50 times faster. >> >> Erik >> >> On Thu, Oct 15, 2015 at 12:27 AM, Gonçalo Mendes Ferreira <go...@sapo.pt> >> wrote: >>> >>> Hi, I've been searching the mailing list archive but can't find an answer >>> to >>> this. >>> >>> What is currently the number of playouts per thread per second that the >>> best >>> programs can do, without using the GPU? >>> >>> I'm getting 2075 in light playouts and just 55 in heavy playouts. My >>> heavy >>> playouts use MoGo like patterns and are probability distributed, with >>> liberty/capture counts/etc only updated when needed, so it should be >>> pretty >>> efficient. >>> >>> What would be a good ballpark for this? >>> >>> Thank you, >>> Gonçalo F. >>> _______________________________________________ >>> Computer-go mailing list >>> Computer-go@computer-go.org >>> http://computer-go.org/mailman/listinfo/computer-go >> >> _______________________________________________ >> Computer-go mailing list >> Computer-go@computer-go.org >> http://computer-go.org/mailman/listinfo/computer-go > > > _______________________________________________ > Computer-go mailing list > Computer-go@computer-go.org > http://computer-go.org/mailman/listinfo/computer-go _______________________________________________ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
