Author: Robert Hyatt
Date: 08:46:28 02/08/04
Go up one level in this thread
On February 08, 2004 at 00:19:28, Pham Hong Nguyen wrote: >On February 07, 2004 at 23:35:01, Robert Hyatt wrote: > >>On February 07, 2004 at 22:03:25, Pham Hong Nguyen wrote: >> >>>I have seen that in CCT6 Crafty used only 386 MB for hash table on a machine >>>with 8 GB physical memory. >> >>Where did you see this? It isn't correct. I actually used 2x that much memory >>as you can see in the cct6 log files on my ftp machine... > >Oops, that information I pick up from address: http://www.vrichey.de/cct6/ > >>It means that a huge memory (at least 7 GB) is almost >>>redundant. I think in coming time, the situation will be worse: more physical >>>memory could not be used for chess engines. I have been thinking some ways of >>>using large size of memory and here may be one: load all 3-4 EGTBs into memory >>>(near enough - need little more memory or some selections of EGTBs). Thus, >>>instead of searching on HDD, we can search on memory. Some good programs (like >>>Crafty) can develop some methods to look up EGTBs not only in main search but in >>>qsearch. >>> >>>Just my two cents. :) >>>What do you comment? >>>+Pham >> >> >>Linux does this already. If you have extra memory, it will cache up the >>filesystem blocks quite readily to avoid doing additional I/O. That was one >>reason I avoided using all of memory for hash. > >A good news :) > >But how about search in qsearch? Do you think the use of EGTBs in qsearch can >help Crafty be stronger? No. I used to do this. But what can happen is that your search can slow to a few hundred nodes per second. If you can't see how to win with the reduced depth, it is likely you will stumble into "how to lose" because the depth will be so limited, you can get killed tactically..
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.