Very nice speed up Goncalo! This prompted me to check my playout speed and
with the recent addition of 3x3 patterns I'm now down to 6pps on 19x19.
Whoops! ;) I may need to do some optimisations ...
Urban
On Fri, Oct 16, 2015 at 1:09 AM, Gonçalo Mendes Ferreira
wrote:
> Thanks
vid Fotland
Sent: 15 October 2015 06:51
To: computer-go@computer-go.org
Subject: Re: [Computer-go] Playout speed... again
In 2008 Many Faces was getting about 25k light playouts per second on 19x19.
Today it gets 2500 playouts per second on one thread of an i7-3770. I don’t
use a probabil
On Wed, Oct 14, 2015 at 06:00:56PM -0700, Dusty Leary wrote:
> The trick to avoid recursively counting liberties:
> Track the liberties for a group/chain using a simplified data structure
> that looks like struct ChainLibertyInfo { int liberty_count; int
> liberty_sum; int liberty_sum_squares; }
>
Thanks everyone for your responses. This is followup after implementing
Dusty Leary's very complete suggestion.
My program is now running 547 playouts/sec and thread, but a lot of
optimizations were removed so I'm sure there's space for growth here. It
is now spending 75% of the time in the
.org
> Subject: Re: [Computer-go] Playout speed... again
>
> Did I read that correctly? The number of playouts per second for Many
> Faces has gone DOWN by a factor of 10? (25,000 -> 2,500) Presumably do to
> the playouts being heavier.
>
> Simon
>
>
>
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
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 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
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
This reply is to both Erik and Petr,
I was running a profile on the program just now. It spends about 90%
updating information to speed up the playout, these are captures and
liberties after play and the resulting 3x3 codified part of the board.
These are updated when needed, so about 4-8
You are noting that you spend most of your time in counting liberties. I
am not an expert at computer Go, but I know a little bit about this so I
can write an answer for you.
There is a paper out there written by someone who is probably on this list
that talks about a few efficient
Hi,
You looks not using incremental-updating approach. This makes
everything faster.
Hideki
Goncalo Mendes Ferreira: <561eee9d.4030...@sapo.pt>:
>This reply is to both Erik and Petr,
>
>I was running a profile on the program just now. It spends about 90%
>updating information to speed up
Hi!
On Wed, Oct 14, 2015 at 11:27:27PM +0100, Gonçalo Mendes Ferreira 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?
>
>
go.org] On Behalf
> Of Gonçalo Mendes Ferreira
> Sent: Wednesday, October 14, 2015 3:27 PM
> To: [mailing list] Computer Go
> Subject: [Computer-go] Playout speed... again
>
> Hi, I've been searching the mailing list archive but can't find an answer
> to this.
>
> What is
13 matches
Mail list logo