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
Hi Casper,
I use the latest Java (1.50.09 and 1.50.06) on both of my machines
which are WINXP SP2 and WIN2K SP5 and the memory
behaviour is the same on both.
If you read above, Tony Thomas did verify my findings.
(I can upload a screenshot from my taskmanager
if you like
My settings.ini is also not corrupted of course.
Not using the own book is no great choice for me and
I never use Arena but strict WB.
At least it seems I can drop the memory with Jims build
to something like 160MB, which is ok for me.
(It seems loading the book really needs a lot of memory
already)
I wonder why you don't have that phenomen in XP 64?
Did you really look at teh taskmanager _during_ a game
or a _while_ after start?
Well maybe memory allocation in 64 bit is different...
Best regards,
Guenther
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?)