Re: [gnugo-devel] Parallelizing GNU Go

[Dave Denholm]

Arend Bayer <address@hidden> writes:

> Dave wrote:
> 
> > Paul writes:
> >
> > > Dave Denholm wrote:
> >
> > > > Depending on what happens with hyper-threading...
> > > > Also depends on whether gnugo is cpmpute bound or memory bound.
> > >
> > > i believe it's mostly memory-bound, but who knows :) hyper-threading might
> > > become a good reason for going threaded but it is not at the moment 
> > > certainly.
> > >
> >
> > Hmm - if it really is memory bound, then running two threads might
> > be *slower* than one thread on a multi-cpu machine : memory
> > thrashing may dominate.
> 
> My assumption is that GNU Go is mostly CPU bound, with the exception
> (of course) of DFA matching (scan_for_patterns), which is memory latency
> bound.
> 
> I base this impression on a few runs witch cachegrind, but it might well
> be that I misinterpreted s.th.
> 


I've been meaning to have a look at cachegrind, but have never had
a chance. Is there any brief summary or hot-spot output that
could be usefully posted ?


dd
-- 
address@hidden          http://www.insignia.com