A: It will depend on the computer you use, but here is the general idea.
If you use these options often, you can store them as GTP text commands in a file such as mysettings.gtp and add a program to [GoGui] which executes as <path>/fuego -config mysettings.gtp
Watch the shell - open with thew command tools-GTP shell to see which GTP commands correspond to each of the settings above. Then simply copy the ones you want into the GTP text file.
A: You can choose any time limit. The more time, the stronger it will play. For very long time limits, you may want to adjust other parameters such as amount of memory.
A: The amount of memory required is a function of the speed of your machine, the number of threads used, and the search time. Faster machines, more threads, and longer search times all require more memory. If you run out of memory during a search, Fuego will run over the tree and prune out lines with a small number of visits, and then continue on with the search. In general, however, the more memory the better.
There are two ways to set the amount of memory Fuego can use. The easiest way is to use the command Uct Max Memory, which takes as an argument the amount of memory you want to allocate to Fuego.
E.g.
uct_max_memory 1000000000
would give Fuego 1GB of memory.
The other way is to figure out the node limit manually and set it. The problem is that the size of a node depends on the size of built in types
E.g.
uct_param_search max_nodes 10000000
would allocate 10 Million nodes, but it depends on the machine how much space that takes. Under Linux, you can run top and see how much memory the fuego process takes, and then adjust.
A: The parameter uct_param_search number_threads should be equal to the number of cores, e.g.
uct_param_search number_threads 2
This can go e.g. in a config file, or you can set it in [GoGui] in the Uct Param Search dialog. For best performance, play with pondering on, and reuse the subtree from the previous search.
uct_param_player ponder 1
uct_param_player reuse_subtree 1
Regarding memory, using as much as possible is good rule of thumb. So cases 1 and 2 should use ~1GB, and 3 ~4GB.