I am running Windows XP Pro 64 bit
4 gigs Ram
Q6600
Anyone have any ideas why there is not a kns increase in these two examples?
thanks kburcham
Deep Shredder 11 x32
2048 hash
10/23 0:00 -0.71 1.Kb1 Rdg8 (2.185.024) 2411
11/28 0:01 -0.91 1.Kb1 Rdg8 (3.728.829) 2435
12/29 0:04 -1.04 1.Kb1 Kb8 (11.539.630) 2495
13/31 0:10 -0.99 1.Kb1 Kb8 (27.073.952) 2529
14/30 0:14 -1.01 1.Kb1 Kb8 (37.784.342) 2534
15/34 0:23 -1.03 1.Kb1 Kb8 (59.036.183) 2549
16/40 1:08 -1.13 1.Kb1 Kb8 (176.873.302) 2568
17/41 1:49 -1.14 1.Kb1 Kb8 (288.380.785) 2623
18/46 3:53 -1.20 1.Kb1 Kb8 (623.282.871) 2664
19/45 6:43 -1.19 1.Kb1 Kb8 (1.093.846.068) 2711
best move: Kc1-b1 time: 9:42.375 min n/s: 2.735.529 CPU 399.8% n/s(1CPU): 684.224 nodes: 1.593.019.043
Deep Shredder 11 x64
2048 hash
10/28 0:01 -0.84 1.Kb1 Kb8 (2.401.522) 2401
11/30 0:01 -0.84 1.Kb1 Kb8 (4.583.585) 2425
12/32 0:03 -0.92 1.Kb1 Kb8 (9.687.996) 2431
13/33 0:07 -0.96 1.Kb1 Kb8 (18.573.506) 2492
14/37 0:13 -1.16 1.Kb1 d5 (35.468.271) 2561
14/37 0:22 -1.10 1.Rde1 Kb8 (56.741.197) 2562
15/34 0:32 -1.15 1.Rde1 Kb8 (83.288.194) 2595
16/35 0:47 -1.15 1.Rde1 Kb8 (124.337.570) 2628
17/41 1:16 -1.19 1.Rde1 Kb8 (202.557.906) 2643
18/39 2:46 -1.24 1.Rde1 Kb8 (445.406.883) 2668
19/48 6:45 -1.19 1.Rde1 Kb8 (1.089.154.319) 2689
best move: Rd1-e1 time: 15:29.703 min n/s: 2.712.920 CPU 399.8% n/s(1CPU): 678.569 nodes: 2.522.125.577
Got any ideas. not getting speed up with Shredder x64
Moderator: Ras
-
kgburcham
- Posts: 2016
- Joined: Sun Feb 17, 2008 4:19 pm
-
IWB
- Posts: 1539
- Joined: Thu Mar 09, 2006 2:02 pm
Re: Got any ideas. not getting speed up with Shredder x64
Hello,
there are several resons why you do not see anything
1. (and most important) Shredder is not a bitboard engine. You do not get Speedups for 64 bit like all these to Bitbases converted Fruits!
2. One position is much too less to judge anything. Make it 10 or 20 and calculate the average
(2a. Is your position an endgame position where the most of the calculation comes from the Tbs? In that case the CPU is waiting for the HD)
3. Measuring with more than one core make it even more difficult, as you may get different results every time you run it.
4. Measuring nodes is the wrong way, you should look for "time to depth"!
So if you really want to measure a speedup, make a set of testpositions, run only with one thred to a defined depth. Summerize the times and divide it by the number of positions.
I personaly doesnt have the 32 bit Version installed anymore but I remember that I once saw an overall +10% shorter time to depth.
Bye
Ingo
PS: Do BB engines get a speedup from 64bit OSs or are they just handicaped by 32bit OSs. Thinking that way means, that NON BB engines are nearly allways at there optimum.
there are several resons why you do not see anything
1. (and most important) Shredder is not a bitboard engine. You do not get Speedups for 64 bit like all these to Bitbases converted Fruits!
2. One position is much too less to judge anything. Make it 10 or 20 and calculate the average
(2a. Is your position an endgame position where the most of the calculation comes from the Tbs? In that case the CPU is waiting for the HD)
3. Measuring with more than one core make it even more difficult, as you may get different results every time you run it.
4. Measuring nodes is the wrong way, you should look for "time to depth"!
So if you really want to measure a speedup, make a set of testpositions, run only with one thred to a defined depth. Summerize the times and divide it by the number of positions.
I personaly doesnt have the 32 bit Version installed anymore but I remember that I once saw an overall +10% shorter time to depth.
Bye
Ingo
PS: Do BB engines get a speedup from 64bit OSs or are they just handicaped by 32bit OSs. Thinking that way means, that NON BB engines are nearly allways at there optimum.
kgburcham wrote:I am running Windows XP Pro 64 bit
4 gigs Ram
Q6600
Anyone have any ideas why there is not a kns increase in these two examples?
thanks kburcham
Deep Shredder 11 x32
2048 hash
10/23 0:00 -0.71 1.Kb1 Rdg8 (2.185.024) 2411
11/28 0:01 -0.91 1.Kb1 Rdg8 (3.728.829) 2435
12/29 0:04 -1.04 1.Kb1 Kb8 (11.539.630) 2495
13/31 0:10 -0.99 1.Kb1 Kb8 (27.073.952) 2529
14/30 0:14 -1.01 1.Kb1 Kb8 (37.784.342) 2534
15/34 0:23 -1.03 1.Kb1 Kb8 (59.036.183) 2549
16/40 1:08 -1.13 1.Kb1 Kb8 (176.873.302) 2568
17/41 1:49 -1.14 1.Kb1 Kb8 (288.380.785) 2623
18/46 3:53 -1.20 1.Kb1 Kb8 (623.282.871) 2664
19/45 6:43 -1.19 1.Kb1 Kb8 (1.093.846.068) 2711
best move: Kc1-b1 time: 9:42.375 min n/s: 2.735.529 CPU 399.8% n/s(1CPU): 684.224 nodes: 1.593.019.043
Deep Shredder 11 x64
2048 hash
10/28 0:01 -0.84 1.Kb1 Kb8 (2.401.522) 2401
11/30 0:01 -0.84 1.Kb1 Kb8 (4.583.585) 2425
12/32 0:03 -0.92 1.Kb1 Kb8 (9.687.996) 2431
13/33 0:07 -0.96 1.Kb1 Kb8 (18.573.506) 2492
14/37 0:13 -1.16 1.Kb1 d5 (35.468.271) 2561
14/37 0:22 -1.10 1.Rde1 Kb8 (56.741.197) 2562
15/34 0:32 -1.15 1.Rde1 Kb8 (83.288.194) 2595
16/35 0:47 -1.15 1.Rde1 Kb8 (124.337.570) 2628
17/41 1:16 -1.19 1.Rde1 Kb8 (202.557.906) 2643
18/39 2:46 -1.24 1.Rde1 Kb8 (445.406.883) 2668
19/48 6:45 -1.19 1.Rde1 Kb8 (1.089.154.319) 2689
best move: Rd1-e1 time: 15:29.703 min n/s: 2.712.920 CPU 399.8% n/s(1CPU): 678.569 nodes: 2.522.125.577