Closed GoogleCodeExporter closed 9 years ago
If the Last update timer has long time like over 30 minutes in it on rate of
4000 games/sec, then its pretty much solved. Shorten the deadline time close to
the achieved build time to get faster computation.
Original comment by Jussi.Pa...@gmail.com
on 24 Oct 2010 at 12:53
The logic behind your suggestion fails. If the program doesn't know the best
build, how can it know how long it will take to get it? And if the program
knows the best possible build, why doesn't it print it out?
The only thing you can do is say: I don't want to wait any longer and assume
that the build I have right now is propably good enough for me.
Original comment by azzur...@gmail.com
on 24 Oct 2010 at 1:06
Original comment by azzur...@gmail.com
on 25 Oct 2010 at 4:08
More or less: If we could divine how good the build was, then we wouldn't need
the program.
Original comment by Frit...@gmail.com
on 6 Nov 2010 at 1:03
Original issue reported on code.google.com by
sergey...@gmail.com
on 23 Oct 2010 at 10:05