Glaurung 2.2 UCI parameters - explanations?

Discussion of anything and everything relating to chess playing software and machines.

Moderator: Ras

Kaj Soderberg

Re: Glaurung 2.2 UCI parameters - explanations?

Post by Kaj Soderberg »

Tord Romstad wrote:
Kaj Soderberg wrote:
krazyken wrote:Hmm, so probably you have a Penryn processor. Is the Windows computer you are comparing to also a laptop?
Hello Kaj,

As far as I can see, you didn't answer the above question from Kenny. It's an important question: Unless the Windows computer you are comparing to also uses a laptop CPU, it is no surprise that chess programs runn slower on your MacBook Pro.
I wonder if there is a considerable difference in the quality of the compiles between the windows and mac version.
I tend to think you are right about the compiles. I've been doing some reading about that stuff, and what i see is that there can be significant speed differences depending on compiles. Maybe for the Mac there are some constraints that are difficult to master, or the worse alternative would be that programmers do not pay as much attention to product quality for the Mac and other smaller platforms than for Windows. As i cannot really believe that the latter option is the case, my guts says here is work to do on the technical side of things.
The Leopard version of Glaurung is compiled using the Intel compiler (unlike the Tiger version, which is compiled with gcc), and is very fast. What N/s count do you get with a single thread from the opening position? I get 1.14 MN/s on my MacBook Core 2 Duo 2.4 GHz.

Tord
Hi Tord,

Both are laptops using Core 2 duos as i told Kenny.
Glaurung 2.1 at 1 thread gives about 610 kn/s from the opening position on my MacBook Pro at 2x2,53 ghz. Definitely lower than on your Mac. Your kn/s are closer to what i would have expected.

Kaj
Kaj Soderberg

Re: Glaurung 2.2 UCI parameters - explanations?

Post by Kaj Soderberg »

krazyken wrote:
Kaj Soderberg wrote:
I tend to think you are right about the compiles. I've been doing some reading about that stuff, and what i see is that there can be significant speed differences depending on compiles. Maybe for the Mac there are some constraints that are difficult to master, or the worse alternative would be that programmers do not pay as much attention to product quality for the Mac and other smaller platforms than for Windows. As i cannot really believe that the latter option is the case, my guts says here is work to do on the technical side of things.

Cheers,

Kaj
As far as different compiles go, compiles for Windows and compiles for Mac are frequently done by different people. Some are much better at optimizing than others it seems.
One thing I did see, A MacBook will run slower if you are running it without a battery. You aren't one of the people who likes to take the battery out are you?
Nope, the battery is still in there.

Kaj
Tord Romstad
Posts: 1808
Joined: Wed Mar 08, 2006 9:19 pm
Location: Oslo, Norway

Re: Glaurung 2.2 UCI parameters - explanations?

Post by Tord Romstad »

Kaj Soderberg wrote:Hi Tord,

Both are laptops using Core 2 duos as i told Kenny.
Glaurung 2.1 at 1 thread gives about 610 kn/s from the opening position on my MacBook Pro at 2x2,53 ghz.
In that case, something is definitely wrong, at least if you are using the Glaurung binary from my web site. If the same pattern holds for other chess programs, I suspect that your CPU is not running at full speed, possibly because of some sort of hardware problem.

Tord
Kaj Soderberg

Re: Glaurung 2.2 UCI parameters - explanations?

Post by Kaj Soderberg »

Tord Romstad wrote:
Kaj Soderberg wrote:Hi Tord,

Both are laptops using Core 2 duos as i told Kenny.
Glaurung 2.1 at 1 thread gives about 610 kn/s from the opening position on my MacBook Pro at 2x2,53 ghz.
In that case, something is definitely wrong, at least if you are using the Glaurung binary from my web site. If the same pattern holds for other chess programs, I suspect that your CPU is not running at full speed, possibly because of some sort of hardware problem.

Tord
Yep, as i see now at around 50% speed. Back to the Mac store this week.
Thanks Tord.

Kaj
krazyken

Re: Glaurung 2.2 UCI parameters - explanations?

Post by krazyken »

this may be worth checking:
Open your System Preferences and click Energy Saver. In Energy Saver, click the Options tab. Now check the setting for Processor Performance. If it’s set to Reduced, change it to Highest.
Kaj Soderberg

Re: Glaurung 2.2 UCI parameters - explanations?

Post by Kaj Soderberg »

krazyken wrote:this may be worth checking:
Open your System Preferences and click Energy Saver. In Energy Saver, click the Options tab. Now check the setting for Processor Performance. If it’s set to Reduced, change it to Highest.
OK, thanks Kenny.
I'll have a look at this when the Mac comes back from the hardware doctor.

Cheers,
Kaj
Kaj Soderberg

Glaurung 2.2 UCI parameters and Smaug

Post by Kaj Soderberg »

Hi Tord and Kenny,

Just thought i'd let you know that all is well with the Mac after changing the hard drive and the battery, and i'm seeing some awesome Glaurung chess almost at daily basis. An aggressive bastard it is, and therefore great fun.
Looking forward to what the Smaug development will bring us.

Cheers,
Kaj
ernest
Posts: 2053
Joined: Wed Mar 08, 2006 8:30 pm

Re: Glaurung 2.2 UCI parameters - explanations?

Post by ernest »

Jim Ablett wrote:I compiled (by request a while ago) win32 versions of Glaurung & Stockfish with reduced uci parameters which fit in 16:9 screens.
Download:
Glaurung 2.2 16:9
http://www.mediafire.com/?1oyxnkyyjyi
Unfortunately, Jim, this glaurung22_(16-9)_win32_ja.exe version (01/01/2009) does not behave the same as your original glaurung22_win32_ja.exe (20/12/2008) :o

Here are 2 examples (running on 1 cpu only, for reproducibility, and 512 MB hash):

1. Start_position
rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1

Code: Select all

Analysis by Glaurung 2.2 JA:
1.Nf3 Nf6 2.d4 e6 3.e3 d5 4.Nc3 Bd6 5.Bd3 Nc6 6.0-0 0-0 7.e4 Bd7 
  =  (0.13)   Depth: 14   00:00:02  1752kN
1.e4 Nf6 2.e5 Nd5 3.Nf3 d6 4.Bc4 Nb6 5.Bd3 Nc6 6.exd6 cxd6 7.0-0 Nd5 
  +/=  (0.43)   Depth: 14   00:00:04  3964kN
1.e4 e5 2.Nf3 Nf6 3.Nxe5 d6 4.Nf3 Nxe4 5.Be2 Be7 6.d3 Nf6 7.0-0 0-0 8.Nc3 
  +/=  (0.49)   Depth: 15   00:00:07  7451kN
1.e4 e5 2.Nf3 Nf6 3.Nxe5 d6 4.Nf3 Nxe4 5.Nc3 Nxc3 6.dxc3 Be7 7.Bd3 Nc6 8.0-0 0-0 9.Be3 
  +/=  (0.39)   Depth: 16   00:00:11  11430kN
1.e4 e5 2.Nf3 Nf6 3.Nxe5 d6 4.Nf3 Nxe4 5.Bd3 Nf6 6.0-0 Be7 7.Nc3 0-0 8.Re1 Nc6 9.Ng5 
  +/=  (0.39)   Depth: 17   00:00:22  22167kN
1.e4 e5 2.Nf3 Nf6 3.Nxe5 d6 4.Nf3 Nxe4 5.Bb5+ c6 6.Bd3 Nc5 7.Be2 Be7 8.d4 Ne4 9.0-0 0-0 10.Nc3 
  +/=  (0.43)   Depth: 18   00:00:45  45872kN
1.e4 e5 2.Nf3 Nf6 3.Nxe5 d6 4.Nf3 Nxe4 5.Bd3 Nf6 6.0-0 Be7 7.Nc3 0-0 8.Be2 Nc6 9.d4 Bf5 10.Bf4 
  +/=  (0.35)   Depth: 19   00:01:28  90079kN
1.e4 e5 2.Nf3 Nf6 3.Nxe5 d6 4.Nf3 Nxe4 5.d3 Nf6 6.d4 d5 7.Bb5+ c6 8.Bd3 Bb4+ 9.c3 Qe7+ 10.Ne5 Bd6 11.0-0 Bxe5 12.dxe5 Qxe5 
  +/=  (0.39)   Depth: 20   00:03:17  202mN

Analysis by Glaurung 2.2 JA (16-9):
1.Nf3 Nf6 2.Nc3 Nc6 3.d4 d5 4.e3 e6 5.Bb5 Bd6 6.0-0 0-0 7.Bxc6 bxc6 8.Bd2 
  =  (0.25)   Depth: 14   00:00:00  656kN
1.Nf3 Nf6 2.Nc3 Nc6 3.d4 e6 4.e4 Bb4 5.Bd3 0-0 6.0-0 d5 7.exd5 exd5 8.Bf4 Bxc3 9.bxc3 
  +/=  (0.35)   Depth: 15   00:00:01  1197kN
1.Nf3 Nf6 2.Nc3 d5 3.e3 e6 4.Bb5+ c6 5.Bd3 Bd6 6.e4 dxe4 7.Nxe4 Nxe4 8.Bxe4 0-0 9.0-0 
  =  (0.13)   Depth: 16   00:00:03  3094kN
1.e4 Nf6 2.Nc3 Nc6 3.Nf3 e6 4.d4 Bb4 5.Bd3 0-0 6.0-0 d5 7.exd5 exd5 8.Bf4 Bxc3 9.bxc3 
  +/=  (0.35)   Depth: 16   00:00:05  4911kN
1.e4 Nf6 2.e5 Nd5 3.Nc3 Nxc3 4.dxc3 Nc6 5.Nf3 e6 6.Bb5 Be7 7.0-0 0-0 8.Bf4 a6 9.Bxc6 dxc6 10.Nd4 
  +/=  (0.33)   Depth: 17   00:00:11  11099kN
1.e4 Nf6 2.e5 Nd5 3.Nc3 Nxc3 4.dxc3 d6 5.Nf3 Bg4 6.h3 Be6 7.Ng5 Nc6 8.Bb5 Bd7 9.0-0 Nxe5 10.Qd5 
  +/=  (0.35)   Depth: 18   00:00:20  20068kN
1.e4 e6 2.Nc3 Nf6 3.e5 Nd5 4.Nxd5 exd5 5.d4 Nc6 6.Nf3 Be7 7.c4 dxc4 8.Bxc4 0-0 9.0-0 d5 10.Bd3 Bg4 
  +/=  (0.35)   Depth: 19   00:01:11  72169kN
1.e4 e6 2.d4 d5 3.exd5 exd5 4.Nf3 Nf6 5.Bb5+ c6 6.Bd3 Bb4+ 7.c3 Qe7+ 8.Be3 Bd6 9.0-0 0-0 10.Nbd2 Na6 
  +/=  (0.35)   Depth: 20   00:02:12  134mN
2. Winning move g4!
r3r1k1/5pb1/1pp1q1p1/4PbBp/p2P3Q/P1N4P/1P3RP1/3R3K w - - 0 1

Code: Select all

Analysis by Glaurung 2.2 JA:  
1.Kg1 Ra7 2.Rc1 Ra5 3.g4 hxg4 4.hxg4 Bxg4 5.Ne4 Rd5 6.Bf6 Rxd4 7.Bxg7 Kxg7 
  +/=  (0.35)   Depth: 12   00:00:02  2250kN
1.Kg1 Ra7 2.Rc1 Qd7 3.Ne4 Bxe4 4.Qxe4 c5 5.Be3 cxd4 6.Bxd4 Qb5 7.Qe2 Qxe2 8.Rxe2 
  =  (0.19)   Depth: 13   00:00:03  3238kN
1.g4 hxg4 2.hxg4 Bxg4 3.Rg1 Bf5 4.Rh2 Ra7 5.Bd8 c5 6.dxc5 Qc6+ 7.Rgg2 Bxe5 
  +/=  (0.47)   Depth: 13   00:00:04  3810kN
1.g4 hxg4 2.hxg4 Bxg4 3.Rg1 Bf5 4.Rh2 Ra7 5.Bc1 c5 6.Qh7+ Kf8 7.Bh6 f6 8.Qh8+ Qg8 9.Bxg7+ Rxg7 10.exf6 Qxh8 11.Rxh8+ Rg8 12.Rxg8+ Kxg8 13.dxc5 bxc5 14.Nxa4 
  +/=  (0.60)   Depth: 14   00:00:04  4356kN
1.g4 hxg4 2.hxg4 Bxg4 3.Rg1 Bf5 4.Rh2 Ra7 5.Rf1 Rd7 6.Qh7+ Kf8 7.Bh6 f6 8.exf6 Qxf6 9.Qh8+ Kf7 
  +/=  (0.68)   Depth: 15   00:00:05  5695kN
1.g4 hxg4 2.hxg4 Bxg4 3.Rdf1 Bh5 4.Bf6 c5 5.dxc5 bxc5 6.Ne4 Qg4 7.Qxg4 Bxg4 8.Bxg7 Kxg7 9.Rxf7+ Kh6 10.Nf6 
  +/=  (0.52)   Depth: 16   00:00:10  9814kN
1.g4 hxg4 2.hxg4 Bxg4 3.Rg1 Bh5 4.Ne4 f5 5.Nf6+ Kf7 6.Nxe8 Rxe8 7.Rgg2 Kf8 8.Bd8 c5 9.dxc5 bxc5 10.Rd2 Bxe5 11.Qxa4 
  +/-  (0.84)   Depth: 17   00:00:27  27278kN
1.g4 hxg4 2.hxg4 Bxg4 3.Rg1 Bh5 4.Ne4 f5 5.Nf6+ Kf7 6.Nxe8 Rxe8 7.Rgg2 Kf8 8.Bd8 c5 9.dxc5 bxc5 10.Rd2 Bxe5 11.Qxa4 
  +/-  (0.84)   Depth: 18   00:00:40  40948kN
1.g4 hxg4 2.hxg4 Bxg4 3.Rg1 Bh5 4.Ne4 f5 5.Nf6+ Kf7 6.Nxe8 Rxe8 7.Qf4 Kg8 8.Bh6 Bg4 9.Kh2 Bxh6 10.Qxh6 c5 11.Rxg4 fxg4 12.Rf6 
  +/=  (0.58)   Depth: 19   00:01:53  116mN

Analysis by Glaurung 2.2 JA (16-9):   
1.Kg1 Ra7 2.Rdd2 Ra5 3.Rf3 Qd7 4.Rf1 Ra6 5.Bf6 Bxf6 6.Qxf6 Ra5 7.Qg5 
  =  (0.15)   Depth: 12   00:00:01  843kN
1.Kg1 Ra7 2.Rdd2 Ra5 3.Rf3 Rf8 4.Ne4 c5 5.Nd6 cxd4 6.Be7 Rfa8 7.Nxf5 gxf5 8.Rxd4 Rxe5 
  +/=  (0.29)   Depth: 13   00:00:02  1972kN
1.Kg1 Ra7 2.Rdd2 Ra5 3.Rf3 Qd7 4.Ne4 Rd5 5.Nf6+ Bxf6 6.Bxf6 c5 7.Rf4 cxd4 8.Rdxd4 Rxd4 9.Rxd4 
  =  (0.23)   Depth: 14   00:00:03  3164kN
1.Kg1 Ra7 2.Rdd2 Ra5 3.Rf1 Qd7 4.Ne4 Rd5 5.Nf6+ Bxf6 6.Bxf6 c5 7.Rfd1 cxd4 8.Rxd4 Rxd4 9.Rxd4 
  =  (0.23)   Depth: 15   00:00:05  5382kN
1.Kg1 Ra7 2.Rdd2 Ra5 3.Rf1 Qd7 4.Ne4 Rd5 5.Nf6+ Bxf6 6.Bxf6 c5 7.Rf4 cxd4 8.Rdxd4 Rxd4 9.Rxd4 Qb5 
  +/=  (0.27)   Depth: 16   00:00:12  12735kN
1.Kg1 c5 2.Bf6 Bxf6 3.exf6 cxd4 4.Qxd4 Qb3 5.Rfd2 Kh7 6.Qf4 Rec8 7.Qf2 Rc4 8.Nd5 Rd8 9.Re1 Be4 
  =  (0.23)   Depth: 17   00:00:33  34711kN
1.Rdd2 Ra5 2.Kg1 Qd7 3.Nd1 Qe6 4.Ne3 f6 5.Nxf5 fxg5 6.Nxg7 gxh4 7.Nxe6 Rxe6 8.Rf4 Rd5 9.Rdf2 g5 10.Rf6 Rxf6 11.Rxf6 Rxd4 12.Rxc6 
  +/=  (0.29)   Depth: 17   00:01:15  77427kN
1.Rdd2 Ra5 2.Kg1 Qd7 3.Nd1 Qe6 4.Ne3 f6 5.Nxf5 fxg5 6.Nxg7 gxh4 7.Nxe6 Rxe6 8.Rf4 Rd5 9.Rdf2 g5 10.Rf5 Rxd4 11.Rxg5+ Kh7 12.Rxh5+ Kg6 
  +/=  (0.41)   Depth: 18   00:01:36  99727kN
1.Rdd2 Ra5 2.Kg1 Qd7 3.Bf6 Bxf6 4.Qxf6 Rf8 5.Qg5 Kh7 6.Rf4 f6 7.exf6 Qe6 8.d5 cxd5 9.g4 Qe3+ 10.Rdf2 Qe1+ 11.Rf1 
  +/=  (0.41)   Depth: 19   00:02:27  153mN
User avatar
Jim Ablett
Posts: 2284
Joined: Fri Jul 14, 2006 7:56 am
Location: London, England
Full name: Jim Ablett

Re: Glaurung 2.2 UCI parameters - explanations?

Post by Jim Ablett »

ernest wrote:
Jim Ablett wrote:I compiled (by request a while ago) win32 versions of Glaurung & Stockfish with reduced uci parameters which fit in 16:9 screens.
Download:
Glaurung 2.2 16:9
http://www.mediafire.com/?1oyxnkyyjyi
Unfortunately, Jim, this glaurung22_(16-9)_win32_ja.exe version (01/01/2009) does not behave the same as your original glaurung22_win32_ja.exe (20/12/2008) :o
Hi Ernest,

Looks like removing some of the uci options has altered the the search/eval defaults.
Odd. I would have expected the defaults to be initialized elsewhere.

Thanks, I'll check it out.

Jim.
zamar
Posts: 613
Joined: Sun Jan 18, 2009 7:03 am

Re: Glaurung 2.2 UCI parameters - explanations?

Post by zamar »

Jim Ablett wrote: Looks like removing some of the uci options has altered the the search/eval defaults.
Odd. I would have expected the defaults to be initialized elsewhere.

Thanks, I'll check it out.

Jim.
In Glaurung+derivatives defaults are initialized when ucioptions are loaded. The ones hardcoded in source are meaningless (and often misleading). If you remove uci options you need to manually fix the hardcoded defaults.

Tord said sometime ago that he has plans to fix this.
Joona Kiiski