Le 06/12/2009 à 01:05, Darren Cook a écrit : > You also need to set max_nodes quite high or Fuego will keep stopping to > clear out its tree. I'm setting it to max_games*50, so for 8000: > uct_param_search max_nodes 400000 > > According to my notes fuego uses 75M + (65M per million max_nodes). So > 15 million nodes will use about 1Gb. (That is on 32-bit linux.)
I miss something: max_games and max_nodes are correlated or not ? why do you chose max_nodes = max_games*50 ? is it boardsize dependent ? I guess that either max_games or max_nodes should be specified, but not both (the first reached is the limiting factor ?) (a new param max_memory appeared recently in trunk, i suppose it is the new human understandable limit) So my config is stupid for fuego 0.4 :-) max_games=16.000 max_nodes=15.000.000 (1GB RAM on ia32) i attached my documented config file (with all the options and documentation i found in the list and on fuego.sf.net) Thanks. Alain
############################################################################### # Configuration parameters for fuego # # see : # http://fuego.svn.sourceforge.net/viewvc/fuego/trunk/doc/manual/index.html # http://www.cs.ualberta.ca/TechReports/2009/TR09-09/TR09-09.pdf # # This file contains GTP commands # ############################################################################### ############################################################################### # Game rules and settings (may be changed by GUI) ############################################################################### # Go Param # There is one parameter that is interesting to users: # Timelimit is the fixed time limit in seconds to use for a move generation, # if no time settings are used for the game. The default is 10. go_param timelimit 999999 # Change the rules used in the game. # What rules are used by Fuego depends only on the settings in Go Param Rules. go_param_rules ko_rule pos_superko # Go Param Rules # WARNING : Note that entering text in the rules text entry of GoGui's game info dialog is # for storing this information in the file only. It is not transmitted to the Go program # because there is no GTP standard command for setting the rules. # What rules are used by Fuego depends only on the settings in Go Param Rules. go_rules kgs ############################################################################### # uct_param_player ############################################################################### # uct_param_player ponder # Whether to continue the search while waiting for the opponent's move. The default is 0 (=no). # # If this is set to 1, uct_param_player reuse_subtree must also be enabled. uct_param_player ponder 1 # uct_param_player reuse_subtree # Whether to reuse the reusable part of the tree from a previous move generation. The default is 0 (=no). # # Setting this to 1 (=yes) is required if pondering is used, but it also gives a small improvement in playing # strength if pondering is not used. uct_param_player reuse_subtree 1 uct_param_player max_games 16000 # uct_param_player ignore_clock 1 # Guess : take remaining time into account (to prevent time loss and try to use all available time for a game) # Guess2 : "go_param timelimit N" still controls the time for each move, even if ignore_clock is set to 1. uct_param_player ignore_clock 1 ############################################################################### # uct_param_search ############################################################################### # uct_param_search number_threads # The number of threads to use. The default is 1. # # This should be set to the number of cores or CPUs available on the system for # maximum performance. It has been tested with up to 8 cores. uct_param_search number_threads 2 # uct_param_search lock_free # Whether to enable lock-free multithreading. The default is 0 (=no). # # You should enable this on modern Intel or AMD CPUs (with IA-32 and Intel-64 architecture) # if more than two threads are used. # Note that without lock-free search the performance of Fuego can even decrease # if you use more threads. The maximum number of threads that can be used # without a decrease of performance, if the lock-free mode is not used, depends on the board size. # Petr Baudis said : (it makes it) faster - there should be no strength difference if you # limit games number, not time. uct_param_search lock_free 1 # uct_param_search max_nodes (obsoleted by max_memory after 0.4 ?) # Determines the maximum number of nodes in the search tree, and thus the maximum memory to use. # The default is 4000000. # # The node size is 48 bytes on 64-bit computers (and 32 bytes on 32-bit computers). # Fuego maintains two search trees internally. # You should use about 10 000 000 nodes per GB main memory that you want to give to Fuego on 64-bit computers # (and 15 000 000 per GB on 32-bit computers). uct_param_search max_nodes 30000000 # uct_param_search max_memory (introduced after 0.4 ?) # Determines the maximum amount of memory in the search tree, and thus the maximum memory to use. # The default is 512MB. # The example above is using 6GB. Fuego maintains two search trees internally, # so setting max_memory to 512MG gives 256MB to each tree. # The second tree is used for work space if using reuse_subtree, or if the search tree fills # up and nodes with small counts are removed. # uct_param_search max_memory 2500MB # uct_param_search virtual_loss # Petr Baudis : It is a technique for tree # search to try to spread parallel-descending threads to different nodes # by adding a loss to the node when the thread descends through it and # removing it when it is returning back to the root. There is some # search efficiency bonus, though the strength gain was very small # in my measurements. uct_param_search virtual_loss 1 # number_playouts : number of playout per leaf # default is 1 # # value 2 is said to reduce memory contention over a cluster (TR09-09.pdf) # The most interesting of those is probably uct_param_search number_playouts 2. # It was used only on 9 × 9. The benefit of doing two playouts per leaf is to reduce mem- # ory contention, since fewer tree updates are performed. In informal tests before the # competition, this was slightly better than the default of one playout. uct_param_search number_playouts 2 ############################################################################### # Misc. ############################################################################### #go_param debug_to_comment 1 #go_param auto_save (filename) #go_sentinel_file (filename) #sg_param time_mode real
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
