Le Mardi 5 Décembre 2006 20:50, John Tromp a écrit : > On 12/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Mogo would also have a memory problem. The UCT programs build trees > > > in memory. My own program cannot think more than a few minutes > > > without running out of memory - so even the experiment you propose > > > cannot be done. > > > > Yes you are right. For MoGo it is even worst. As all the games we have to > > play > > in are short games, we did not at all "optimize" the memory use, and in > > fact > > MoGo a lot more memory than necessary. I am not totally sure, but I think > > even 1 minute/move is already too much :). Of course, we can be more > > carefull > > with memory usage, but for the moment it is not the higher priority. > > How long would it take Mogo to fill up 16GB of memory on a quad core > opteron machine?
It depends on the speed of your opteron :). Perhaps something like 10 minutes. I think stl vector implementation on my linux box takes much more memory than necessary (I mean using a memory pool, and a big time against memory tradeoff), so perhaps being carefull, with 16 GB we could reach 20 minutes. Sylvain _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
