Dorky 4.1 64-bit - always single-threaded?
Moderators: hgm, Harvey Williamson, bob
Forum rules
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
Dorky 4.1 64-bit - always single-threaded?
I tried values of 1, 2 and 3 for n_cpus but task manager always displayed 25% CPU usage.
True, the problem with false pondering has gone but I now have the feeling that 4.0 also might have played on only 1 core because I don't remember ever seeing 50% with task manager.
Environment: Intel Q6600, 64-bit Vista
True, the problem with false pondering has gone but I now have the feeling that 4.0 also might have played on only 1 core because I don't remember ever seeing 50% with task manager.
Environment: Intel Q6600, 64-bit Vista
Gabor Szots
CCRL testing group
CCRL testing group
Re: Dorky 4.1 64-bit - always single-threaded?
Hi Gabor,
The value set in .ini file for n_cpus will be overridden by the winboard 'cores' command. Is your winboard also configured for > 1 core?
Matt
The value set in .ini file for n_cpus will be overridden by the winboard 'cores' command. Is your winboard also configured for > 1 core?
Matt
Re: Dorky 4.1 64-bit - always single-threaded?
Hi Matt,mmcknight wrote:Hi Gabor,
The value set in .ini file for n_cpus will be overridden by the winboard 'cores' command. Is your winboard also configured for > 1 core?
Matt
I don't know. This was under Arena. I'm going to try to find out how it is under WB.
Gabor
Gabor Szots
CCRL testing group
CCRL testing group
Re: Dorky 4.1 64-bit - always single-threaded?
Hmm, apparently I don't know how to issue a cores command under WB. Under engine options I find max. nr. of CPU's, this is set to 2. When in analysis mode, I press <Alt><1> to issue the command cores=2 but task manager still reports 25%.
Terrible feeling, I've lost almost all my WB knowledge.
Terrible feeling, I've lost almost all my WB knowledge.
Gabor Szots
CCRL testing group
CCRL testing group
Re: Dorky 4.1 64-bit - always single-threaded?
I tried it from the command line and it told me it used 2 cores and in fact tsk manager confirmed that by showing 50%.
I don't know how Arena spoils that, maybe some init string has to be given?
I don't know how Arena spoils that, maybe some init string has to be given?
Gabor Szots
CCRL testing group
CCRL testing group
Re: Dorky 4.1 64-bit - always single-threaded?
Gabor I am not familiar with Arena. If you could send me a .debug file of your arena->dorky interface maybe I could figure out what is happening.
Thanks,
Matt
Thanks,
Matt
- hgm
- Posts: 22274
- Joined: Fri Mar 10, 2006 9:06 am
- Location: Amsterdam
- Full name: H G Muller
- Contact:
Re: Dorky 4.1 64-bit - always single-threaded?
The "Max nr of CPUs" in the Options -> Common Engine... menu dialog should do it. If not, make a winboard.debug file from the engine startup, and post it here. Then I might be able to see what is wrong.SzG wrote:Hmm, apparently I don't know how to issue a cores command under WB. Under engine options I find max. nr. of CPU's, this is set to 2. When in analysis mode, I press <Alt><1> to issue the command cores=2 but task manager still reports 25%.
The command should be "cores 2", btw, without equal sign.
Re: Dorky 4.1 64-bit - always single-threaded?
Hi Gabor. If you are using Arena 3.0, go to Engines->Manage in the main menu (or use the F11 shortcut key). In the Engine Management window, there is a Winboard tab, with a Max. CPUs option. Try setting that option to the number of cores that you have, and see if that works.
Re: Dorky 4.1 64-bit - always single-threaded?
Here is the debug file. Note that I issued cores 2 during analysis but I can't see it appear in the debug.hgm wrote:The "Max nr of CPUs" in the Options -> Common Engine... menu dialog should do it. If not, make a winboard.debug file from the engine startup, and post it here. Then I might be able to see what is wrong.SzG wrote:Hmm, apparently I don't know how to issue a cores command under WB. Under engine options I find max. nr. of CPU's, this is set to 2. When in analysis mode, I press <Alt><1> to issue the command cores=2 but task manager still reports 25%.
The command should be "cores 2", btw, without equal sign.
Code: Select all
recognized 'normal' (-1) as variant normal
recognized 'normal' (-1) as variant normal
WinBoard hgmaster-20110610 + Dorky_41-x64
Reset(1, 0) from gameMode 0
recognized 'normal' (-1) as variant normal
GameEnds(0, (null), 2)
shuffleOpenings = 0
TC string = ':40/155'
mps=40 tc=155000 inc=0
TC string = ':40/155'
mps=40 tc=155000 inc=0
StartChildProcess (dir="C:\Sakk\WB-engines\Dorky") Dorky_41-x64.exe
nice engine proc to 10
577 >first : xboard
protover 2
577 <first : EGTB cache memory = 32M bytes.
577 <first : error reading book file!
577 <first : non-fatal i/o error
593 <first :
593 <first : Dorky Chess v4.1 (2 cpus)
593 <first : by Matthew McKnight
593 <first :
593 <first : W>
593 <first : feature draw=1 setboard=1 analyze=1 ping=1 reuse=1 time=1 playother=1 sigint=0 sigterm=0 smp=1 ics=1 name=1 egt="nalimov" myname="Dorky 4.1" done=1
593 >first : accepted draw
593 >first : accepted setboard
593 >first : accepted analyze
593 >first : accepted ping
593 >first : accepted reuse
593 >first : accepted time
593 >first : accepted playother
593 >first : accepted sigint
593 >first : accepted sigterm
593 >first : accepted smp
593 >first : accepted ics
593 >first : accepted name
593 >first : accepted egt
593 >first : accepted myname
593 >first : accepted done
640 >first : egtpath nalimov C:\Sakk\TB
640 >first : cores 2
640 >first : new
random
640 >first : ics -
640 >first : level 40 2:35 0
640 >first : post
640 >first : hard
640 >first : easy
640 >first : ping 1
640 <first : initializing egtb
640 <first : EGTB already initialized
640 <first : using 2 cpus
640 <first : pong 1
6739 >first : force
6739 >first : analyze
6739 <first : Analyzing... use 'exit' to stop.
6755 <first : starting thread 1
6755 <first : System is SMP
6755 <first : done
6895 <first : 10 6 14 229959 d4 d5 Bg5 f6(HT) Bf4(HT)
7067 <first : 11 5 31 514193 d4 d5 e3 Nf6(HT) Nf3(HT)
7441 <first : 12 5 68 1179122 d4 d5 Bg5 f6(HT) Bf4(HT) Bf5(HT) e3(HT)
8424 <first : 12 10 166 2956032 e4 e6 d4 Nc6 Nf3(HT)
9703 <first : 13 14 294 5317391 e4 e6 d4 d5 e5 Ne7 Nf3 Nd7 Bd2 Nf5 Bd3 c5 dxc5 Bxc5
10764 >first : .
10780 <first : stat01: 402 7413164 14 20 0 a8a8
12776 >first : .
12776 <first : 14 18 602 11179654 e4 e6 Nf3 Nc6 d4 d5 e5 a6 Nc3 Be7 Bf4 g5 Be3 Nb4
12808 <first : stat01: 605 11214194 14 20 0 a8a8
14789 >first : .
14789 <first : stat01: 803 14994804 15 20 0 a8a8
16801 >first : .
16817 <first : stat01: 1006 18992439 15 20 0 a8a8
18595 <first : 15 16 1184 22363104 e4 e6 Nf3 Be7 d4 Nf6 Nc3 O-O Bd3 Nc6
18814 >first : .
18829 <first : stat01: 1207 22793469 15 20 0 a8a8
20826 >first : .
20826 <first : stat01: 1407 26681865 16 20 0 a8a8
22838 >first : .
22838 <first : stat01: 1608 30613965 16 20 0 a8a8
24851 >first : .
24866 <first : stat01: 1811 34742670 16 20 0 a8a8
26863 >first : .
26879 <first : stat01: 2012 38674770 16 20 0 a8a8
28876 >first : .
28876 <first : stat01: 2212 42672405 16 20 0 a8a8
30888 >first : .
30919 <first : stat01: 2416 46473435 16 20 0 a8a8
31153 <first : 16 18 2439 46959277 e4 e6 Nf3 Nc6
32900 >first : .
32900 <first : stat01: 2614 50471070 16 20 0 a8a8
34913 >first : .
34944 <first : stat01: 2818 54479529 17 20 0 a8a8
36925 >first : .
36925 <first : stat01: 3017 58346094 17 20 0 a8a8
38938 >first : .
38938 <first : stat01: 3218 62278194 17 20 0 a8a8
40950 >first : .
40950 <first : stat01: 3419 66406899 17 20 0 a8a8
GameEnds(28, xboard exit, 2)
41309 >first : exit
41309 >first : quit
Gabor Szots
CCRL testing group
CCRL testing group
Re: Dorky 4.1 64-bit - always single-threaded?
Hi Tony,tmokonen wrote:Hi Gabor. If you are using Arena 3.0, go to Engines->Manage in the main menu (or use the F11 shortcut key). In the Engine Management window, there is a Winboard tab, with a Max. CPUs option. Try setting that option to the number of cores that you have, and see if that works.
I use version 2.0.6 where there is no Winboard tab, nor maxCPU option anywhere.
Gabor Szots
CCRL testing group
CCRL testing group
