On Mon, 18 Apr 2005, Paul Pogonyshev wrote:
> I wrote: > > OK, another huge patch makes multi-board GNU Go pass `reading.tst' > > without unexpected results and with exactly the same node counter as > > original. Phew... Had to convert a large number of files just for > > this. > > And now also `connect.tst'. The obvious question: How big is the performance penalty? That's of course s.th. we need to take into account when discussing whether we want this in mainline. Can you say a little more about your general motivation for doing this? Do you plan to make GNU Go mulit-threaded? I certainly don't mind paying 1% or so in performance penalty on uni-processor ssystem for having GNU Go being able to use multple CPUs where they are available. On the other hand, paying 10% for a project that will never get completed... :) Arend _______________________________________________ gnugo-devel mailing list gnugo-devel@gnu.org http://lists.gnu.org/mailman/listinfo/gnugo-devel
