Hi I read http://trac.gnugo.org/gnugo/ticket/24 and the corresponding mail thread. It seems a very important step for GNU Go, (for sizing on SMP/cluster with more or less deep look-ahead, i guess you know this ;) and if i understand well, it could be very usefull for other things.
For example, concerning my experimental twin, it will help me for de-uglyfication, make avalaible both B&W data (instead of my hack where i lose lots of opponent data), and on a 2+ way computer it will make the twin nearly as fast as ordinary gnugo (parallel review_move_reasons), whereas now it is roughly 50% slower. The only thing i can do to help, is testing it on my venerable dual-celeron 400 box. Concerning the performance, +/- 10% will not change the (un-)usability of gnugo on a computer/phone/PDA, and i think it is worth paying that price. Cheers Alain _______________________________________________ gnugo-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnugo-devel
