lotus

previous page: C.6 Running (or building) GNU Chess fails with a message about FIONREAD.
  
page up: GNU Chess and XBoard FAQ
  
next page: D.1 What is XBoard?

C.7 GNU Chess runs way too slow and makes my disk seek wildly.

Headaches Begone! A Systemic Approach To Healing Your Headaches Book

Description

This article is from the GNU Chess and XBoard FAQ, by Tim Mann mann@pa.dec.com with numerous contributions by others.

C.7 GNU Chess runs way too slow and makes my disk seek wildly.

This happens if you don't have enough real memory (RAM) to run GNU
Chess. You may need 16MB or more. You can reduce GNU Chess's memory
requirements by reconfiguring it, or just buy more memory. Some (rather
out of date) suggestions are in the file doc/PORTING from the GNU Chess
source tree.

The following is from Nikhil Nair:

It is perfectly possible to run gnuchess on an 8Mb system. I
would suggest that you don't edit the source (though the
defaults are the definitions of ttblsz or something like that
in src/ttable.h and DEFETABS in src/gnuchess.h), but rather
use the -C and -T command-line options (which even work for
gnuan, though not documented in the manpage). The defaults are
`-C 18001 -T 150001' (for MS-DOS, -T 8001). On my Linux
system, this uses just over 9Mb. From memory, `-C 6001 -T
40001' uses around 3Mb. Fiddle with these and see what results
you get.

Why does GNU Chess use so much memory? The extra memory lets it keep
large hash tables that speed up its search and make it play better, and
a large on-line book that improves opening play. If you have lots of
memory you may want to reconfigure GNU Chess to use *more* than the
default amount.



 

Continue to:

Free Sex Improvement Training at ExperientialSexLab.com







TOP
previous page: C.6 Running (or building) GNU Chess fails with a message about FIONREAD.
  
page up: GNU Chess and XBoard FAQ
  
next page: D.1 What is XBoard?