Moderator: Andres Valverde
Jim Ablett wrote:
Win32 exe including opening book.
http://www.sigmirror.com/files/599/ALF%20CHESS/alf_106_win32.7z
Jim.
Jim Ablett wrote:Hi Tony,
There should definitely be a speed increase
Java compiled to optimized machine code will always be faster than
the Java interpreter.
Jim.
Java compiled to optimized machine code will always be faster than
the Java interpreter.
First, thanks for the logo - I like it!
Can I use on my homepage?
This is actually an old myth, almost every Java interpreter uses Just-in-Time compilation, which means there should only be a constant time difference when you start the program. Unless of course your compiler is better than Java's...
Casper W. Berg wrote:Hi, Guenther
There is two ways to decrease the memory usage:
1) Set the hashsize to something lower in the settings.ini file
I can't understand when you say it has no influence at all - it works on my machine...
2) Disable the book (also in the settings.ini)
The book is loaded in the memory.
Yes, Alf might allocate more memory if the hashtable is full, in order to collect the PV for thinking lines (limited to 5 ply - so it should not be much).
If the memory limit is to provide fairness and not because it's eating all you free memory, then I wouldn't worry...the number of entries is still very low compared to other engines, because my classes are very memory inefficient.
I will try to make it smaller for next release, but I fear a complete rewrite is the only thing that will seriously help, so that's not in the near future...
-Casper
hashsize=300000
java -Xms100m -Xmx150m -jar Alf106.jar
Jim Ablett wrote:
Win32 exe including opening book.
http://www.sigmirror.com/files/599/ALF%20CHESS/alf_106_win32.7z
Jim.
// This is the settings file for the chess engine Alf.
// units are:
// hashsize=roughly number of entries (the number will be the closest prime not near a power of two). (100k = about 12 Mb)
// contempt=(point)decimal number in pawns (this value may be scaled up/down by Alf in timed games)
// boolean options can be "true"/"false"
hashsize=100000
contempt=0.75
postThinking=true
useNullMove=true
useBook=false
bookFile=book106.bin
useFutility=true
useLMR=true
No matter what settings I use either in the settings.ini
or in the command line by Xms/Xmx options Alf always
allocates around 225MB memory for it and uses at least
170MB of this after a while.
BTW what is the exact meaning of the Xms/Xmx commands?
Of course I don't want to disable the book.
(It shouldn't allocate more than 16MB for the book files anyway?
Or does it expand somehow?)
I guess you don't use a WIN OS?
Casper W. Berg wrote:Hi Guenther, thanks for the feedback.No matter what settings I use either in the settings.ini
or in the command line by Xms/Xmx options Alf always
allocates around 225MB memory for it and uses at least
170MB of this after a while.
This sounds very strange...Which version of Java are you using?
Maybe an upgrade will help. But I suggest you use Jim's compilation since it's clearly better
Another possibility is that the settings.ini file is somehow corrupt, in which case a default value of 300k is used as hashsize (you might also get an error message from Alf on startup).BTW what is the exact meaning of the Xms/Xmx commands?
Xms is the initial heap size, and Xmx is the maximum.
If Xmx is exceeded Java should exit with an "out of memory" exception, but these are non-standard options (Java -X to print help on these).Of course I don't want to disable the book.
(It shouldn't allocate more than 16MB for the book files anyway?
Or does it expand somehow?)
Well, if you use Arena you can use one of the Arena books instead.
But no, it should not allocate more as far as I know, but there might be differences between Java versions.I guess you don't use a WIN OS?
I use Win XP 64 ed. and Sun's Java 1.5.
Java uses garbage collection, which usually happens when the system is not heavily loaded, so there might be some differences when memory use drops. There are also settings for that, but I haven't tried them.
I hope that was helpful.
-Casper
Did you really look at teh taskmanager _during_ a game
or a _while_ after start?
Well maybe memory allocation in 64 bit is different...
P.S. I noticed something else which is not WB standard
and should be at least there as an user option.
Alf reports scores only from White POV, under WB it is usual
to report from engines POV.
(E.g. this breaks some analysis tools written for WB PGNs
and the WB evaluation window too... I guess you don't even
know WB 4.27x by Alessandro Scotti?)
Casper W. Berg wrote:Hi,
A new version of my engine "Alf" has been released....
8703 >first : white
8703 >first : go
8712 <first : 1 1 1 1 c2 - c4 (5401.0)
8732 <second: tellicsnoalias set 1 Crafty v20.14 (1 cpus)
8732 <second: pong 1
8913 <first : move c2c4
8913 >second: time 90000
otim 90479
8913 >second: c4
8913 >second: go
AnimateMove: piece 0 slides from 2,1 to 2,3
8994 <second: tellicsnoalias kibitz Hello from Crafty v20.14! (1 cpus)
8994 <second: move e5
Interrupting first
8994 >first : time 90479
otim 90491
8994 >first : e7e5
AnimateMove: piece 6 slides from 4,6 to 4,4
9079 <second: Hint: Nc3
9079 <first : e7e5
9079 <first : 1 1 1 1 Nb1 - c3 (846.0)
xboard: Error: first chess program (java -Xms400m -Xmx600m -jar Alf106a.jar) exited unexpectedly
9079 <second: Hint: Nc3
9079 <first : e7e5
9079 <first : 1 1 1 1 Nb1 - c3 (846.0)
xboard: Error: first chess program (java -Xms400m -Xmx600m -jar Alf106a.jar) exited unexpectedly
Return to Winboard and related Topics
Users browsing this forum: No registered users and 9 guests