I noticed that there was a serious problem in the interface Damage 2011
Could you provide specific information regarding the serious problem of the interface of the Damage GUI.
So I can have a look and where required and/or needed change/improve this.
I noticed that there was a serious problem in the interface Damage 2011
Could you provide specific information regarding the serious problem of the interface of the Damage GUI.
So I can have a look and where required and/or needed change/improve this.
With kind regards,
Bert
Of course. During starting Horizon an empty board appears without divisions. During the game with DXP divisions are keeping still during the game. As regards the DB file, I am finding the file oneself correctly that is in the main folder Engines.
Other Questions;
* There is only 1 instance running of Horizon?
* You start directly Horizon and not via the Damage GUI?
* Could you provide a file-list of the Databases directory?
* What is the memory size of the Notebooks you use?
Other Questions;
* There is only 1 instance running of Horizon?
* You start directly Horizon and not via the Damage GUI?
* Could you provide a file-list of the Databases directory?
* What is the memory size of the Notebooks you use?
Bert
It thanks that you wrote Bert. I answer on your question Bert. What to question first - then programme starts 1 cores. What to question second - this starts programme Horizon and not Damage GUI. What to question third - enclose enclosure. What to question fourth - have three laptops. Two ideally the same laptops about the same parameters - processor I3 350M from 8 GB of the memory of frames DDR 3 1333 . As well as one laptop from processor I7 2670QM from 16 GB of the memory of frames DDR 3 1333.
Thanks for posting.
A little strange that with the 6P DB active the loss rate is even worse, but again this could be pure statistics.
I will get into some Horizon sources the next weeks, and see if there are some easy fixes which result in better play.
About hashtable sizes: I measured the time it takes kingsrow to clear some data in the hashtable, which it does at the beginning of each search. With a 512mb hashtable it takes 300msec. This time subtracts from usable search time, so for quick games a much smaller hashtable will give better performance. Here is a table of recommended hashtable sizes for Kingsrow:
Ed Gilbert wrote:About hashtable sizes: I measured the time it takes kingsrow to clear some data in the hashtable, which it does at the beginning of each search. With a 512mb hashtable it takes 300msec. This time subtracts from usable search time, so for quick games a much smaller hashtable will give better performance. Here is a table of recommended hashtable sizes for Kingsrow:
Search Time Search Threads Hashtable Size
1 sec/move 1 through 8 32 mb
2 sec/move 1 thread 32 mb
2 sec/move 2 or more 64 mb
5 sec/move 1 thread 64 mb
5 sec/move 2 or more 128 mb
10 sec/move 1 thread 128 mb
10 sec/move 2 or more 256 mb
30 sec/move 1 thread 256 mb
30 sec/move 2 or more 512 mb
Ed thanks. And how many you would give to Hashtable Size how the program would use from 8 Search Threads, and the time would be 3 sec/move and 7 sec/move. Very much I firmly am interested in these two times since with such times I am playing against the man.
Ed thanks. And how many you would give to Hashtable Size how the program would use from 8 Search Threads, and the time would be 3 sec/move and 7 sec/move. Very much I firmly am interested in these two times since with such times I am playing against the man.
You can use 64mb for 3sec/move and 128mb for 7sec/move with 8 search threads.
Match KINGSROW - DRAGON (3-move ballots) - 260 party
Kingsrow 1.55 vs. Dragon 4.4.0 (64 bit standaard) 7 wins,6 losses, 241 draws, 6 unknowns
Kingsrow
Opening Book = Best Moves
HashTable Size = 512 MB
DB cache Size = 12000 MB, 6P - New database
CPU 4 = 8 cores
Pondering = Off
Time = 5 Min / 65 Moves
Dragon
Opening Book = Tournament Book
HashTable Size = 512 MB
DB cache Size = 2000 MB, 6P
CPU 4 = 8 cores
Pondering= Off
Time = 5 Min / 65 Moves
Match KINGSROW - DRAGON (3-move ballots) - 158 party from 260 party
Kingsrow 1.55 vs. Dragon 4.4.0 (64 bit standaard) 3 wins,5 losses, 146 draws, 4 unknowns
Kingsrow
Opening Book = Best Moves
HashTable Size = 512 MB
DB cache Size = 12000 MB, 6P - New database
CPU 4 = 8 cores
Pondering = Off
Time = 5 Min / 65 Moves
Dragon
Opening Book = Tournament Book
HashTable Size = 512 MB
DB cache Size = 2000 MB, 6P
CPU 4 = 8 cores
Pondering= Off
Time = 5 Min / 65 Moves
Match played on a computer with the equipment. Processor - Intel Core I7 2670QM, 2.2GHz
Hard disc - SSD Samsung 840 Evo 1 TB
Memory of frames - 16 GB DDR3 1333
System - Windows 7 Home Premium 64 bit Service Pack 1 PL
Match KINGSROW - DRAGON (3-move ballots) - 260 party
Kingsrow 1.55 vs. Dragon 4.4.0 (64 bit standaard) 19 wins,16 losses, 217 draws, 8 unknowns
Kingsrow
Opening Book = Best Moves
HashTable Size = 256 MB
DB cache Size = 12000 MB, 6P - New database
CPU 4 = 8 cores
Pondering = Off
Time = 1 Min / 65 Moves
Dragon
Opening Book = Tournament Book
HashTable Size = 256 MB
DB cache Size = 2000 MB, 6P
CPU 4 = 8 cores
Pondering= Off
Time = 1 Min / 65 Moves
Match KINGSROW - DRAGON (3-move ballots) - 158 party from 260 party
Kingsrow 1.55 vs. Dragon 4.4.0 (64 bit standaard) 12 wins,9 losses, 132 draws, 5 unknowns
Kingsrow
Opening Book = Best Moves
HashTable Size = 256 MB
DB cache Size = 12000 MB, 6P - New database
CPU 4 = 8 cores
Pondering = Off
Time = 1 Min / 65 Moves
Dragon
Opening Book = Tournament Book
HashTable Size = 256 MB
DB cache Size = 2000 MB, 6P
CPU 4 = 8 cores
Pondering= Off
Time = 1 Min / 65 Moves
Match played on a computer with the equipment.
Processor - Intel Core I7 2670QM, 2.2GHz
Hard disc - SSD Samsung 840 Evo 1 TB
Memory of frames - 16 GB DDR3 1333
System - Windows 7 Home Premium 64 bit Service Pack 1 PL
Kingsrow 1.55 vs. Dragon 4.4.0 (64 bit standaard) 4 wins, 3 losses, 148 draws, 3 unknowns
Kingsrow
Opening Book = Best Moves
HashTable Size = 512 MB
DB cache Size = 12000 MB, 6P - New database
CPU 4 = 8 cores
Pondering = Off
Time = 10 Min / 65 Moves
Dragon
Opening Book = Tournament Book
HashTable Size = 512 MB
DB cache Size = 2000 MB, 6P
CPU 4 = 8 cores
Pondering= Off
Time = 10 Min / 65 Moves
Match played on a computer with the equipment.
Processor - Intel Core I7 2670QM, 2.2GHz
Hard disc - SSD Samsung 840 Evo 1 TB
Memory of frames - 16 GB DDR3 1333
System - Windows 7 Home Premium 64 bit Service Pack 1 PL