On Wed, Jan 14, 2015 at 01:26:44PM +0100, Urban Hafner wrote:
> Hey Jason,
>
> thanks. Rust is probably not very well optimised, yet. It hasn't even
> reached 1.0 and there are still many language changes happening. But I
> attribute the slowness to the fact that I'm not used to writing code in
> compiled languages (I'm a web developer). :P But learning how to write
> performant code is half the fun and I guess I still have a bit of work to
> do here.
Note that the mistake I did with Pachi is that I worked hard to optimize
the Go board (playout) code with minimal functionality to perform
a playout correct by the rules, only then discovering how much other
information I need to keep to add some useful heuristics to the playout,
and maybe the hotspots change then.
If I did it again, after picking some really low-hanging optimization
fruit I'd rther focus on implementing playout heuristics, only then
coming back to optimize the board code when it is clear what all
information I need to compute the heuristics efficiently (list of up to
N libs, maybe pre-computed pattern hashes, etc.).
--
Petr Baudis
If you do not work on an important problem, it's unlikely
you'll do important work. -- R. Hamming
http://www.cs.virginia.edu/~robins/YouAndYourResearch.html
_______________________________________________
Computer-go mailing list
[email protected]
http://computer-go.org/mailman/listinfo/computer-go
