According to Dragon Elo setting, Shedder8 = 2805

[Chessqueen]

I Set Komodo Elo = 2805 FIDE and after 50 games at T/C 15/10 so far the score is dead even; I will let it continue until 100 games just to confirm my findings. But to my surprise Komodo Dragon Elo =2805 is holding Shredder8 so far when it is making its move at an average of 2 to 3 seconds while Shredder8 is using its entire T/C of 15/10

[Chessqueen]

I Set Komodo Elo = 2805 FIDE and after 50 games at T/C 15/10 so far the score is dead even; I will let it continue until 100 games just to confirm my findings. But to my surprise Komodo Dragon Elo =2805 is holding Shredder8 so far when it is making its move at an average of 2 to 3 seconds while Shredder8 is using its entire T/C of 15/10

[pgn][Event Dragon Elo = 2805"]
[Site "DESKTOP-OFQ3C0P"]
[Date "2022.06.15"]
[Round "51"]
[White "Dragon-2.6.1-64bit-avx2"]
[Black "Shredder8"]
[Result "1-0"]
[BlackElo "2805"]
[ECO "D12"]
[Opening "Slav"]
[Time "19:11:58"]
[Variation "4.e3 Bf5 5.Nc3 e6 6.Nh4"]
[WhiteElo "2805"]
[TimeControl "900+10"]
[Termination "normal"]
[PlyCount "122"]
[WhiteType "program"]
[BlackType "program"]

1. d4 Nf6 2. c4 c6 3. Nf3 d5 4. e3 Bf5 5. Nc3 e6 6. Nh4 Bg6 7. Nxg6 hxg6 8.
Bd2 Nbd7 9. g3 {(g2-g3 c6-c5 c4xd5) +0.69/8} Bb4 {(Bf8-b4 c4xd5 e6xd5
Bf1-g2 O-O Qd1-b3 Bb4xc3 Bd2xc3 Qd8-c7 Ra1-c1 Rf8-e8 O-O Nf6-e4 Bc3-b4
a7-a5 Bg2xe4 d5xe4 Bb4-c5 Nd7xc5 Qb3xf7+) +0.04/17 81} 10. Qb3 {(Qd1-b3
a7-a5 a2-a3 Bb4xc3 Bd2xc3 Qd8-b6 Qb3-c2 Nf6-e4 Ra1-c1 O-O Bf1-g2 Qb6-d8)
+0.33/10} a5 {(a7-a5 Bf1-e2 O-O O-O Qd8-c7 Nc3-b1 Bb4-e7 Nb1-c3 Nd7-b6
c4xd5 c6xd5 Ra1-c1 Nb6-c4 Be2xc4 Qc7xc4 Qb3xb7 Qc4-b4) +0.05/16 49} 11. a3
{(a2-a3 Bb4xc3 Bd2xc3 Qd8-b6 Qb3-c2 Nf6-e4 Bf1-d3 Nd7-f6 Ke1-f1 O-O Kf1-g2
Ne4xc3 b2xc3) +0.64/11} Bxc3 {(Bb4xc3 Bd2xc3 b7-b6 Bf1-g2 Nf6-e4 Qb3-c2
Nd7-f6 O-O Ra8-c8 Ra1-c1 Nf6-g4 h2-h4 Ng4xf2 Rf1xf2 Rc8-c7) +0.01/17 35}
12. Bxc3 {(Bd2xc3 Qd8-b6 Qb3-c2 Nf6-e4 Bf1-d3 Nd7-f6 Ke1-f1 Ne4xc3 b2xc3
d5xc4 Bd3xc4) +0.53/11} Qc7 {(Qd8-c7 Bf1-g2 O-O O-O Rf8-e8 Ra1-b1 Nf6-e4
Qb3-c2 Nd7-f6 c4-c5 Ne4xc3 b2xc3 b7-b5 c5xb6/ep Nf6-e4 b6xc7 Ne4xc3 Qc2xc3)
+0.01/18 74} 13. Bd3 {(Bf1-d3 Nf6-e4 Bd3xe4 d5xe4 h2-h4 Nd7-f6 a3-a4 O-O
O-O-O Nf6-g4 Qb3-c2) +0.40/9} Ne4 {(Nf6-e4 Qb3-c2 Nd7-f6 O-O-O O-O f2-f3
Ne4xc3 Qc2xc3 Ra8-d8 Kc1-b1 b7-b6 Qc3-c2 c6-c5 c4xd5 Nf6xd5 Bd3xg6 f7xg6
Qc2xg6) +0.11/17 40} 14. Kf1 {(Ke1-f1 Ne4xc3 Qb3xc3) +0.46/10} Ndf6
{(Nd7-f6 Qb3-c2 g6-g5 Kf1-g2 O-O-O c4xd5 e6xd5 f2-f3 Ne4xc3 Qc2xc3 Kc8-b8
h2-h3 Nf6-h5 f3-f4 Nh5xf4+ g3xf4 Qc7xf4 e3xf4) +0.75/15 37} 15. Be1
{(Bc3-e1 a5-a4 Qb3-c2) +0.61/10} Nd6 {(Ne4-d6 c4xd5 e6xd5 Kf1-g1 Nf6-e4
Ra1-c1 Qc7-d7 f2-f3 Ne4-g5 Qb3-b6 Ng5xf3+ Kg1-f1 Nf3xh2+ Kf1-f2 Qd7-h3
Qb6-b4) +0.91/14 32} 16. c5 {(c4-c5 Nd6-f5 Kf1-g2) +0.98/10} Nf5 {(Nd6-f5
Be1-c3 Nf6-g4 Kf1-e2 Ng4xh2 Ra1-e1 Rh8-h6 Qb3-a4 Nh2-g4 Rh1xh6 g7xh6 b2-b3
Ng4xe3 f2xe3 Nf5xg3+ Ke2-f2 Qc7-f4+ e3xf4) +0.69/16 31} 17. Kg2 {(Kf1-g2
O-O Be1-c3 Rf8-b8 Qb3-c2 b7-b6 h2-h4 b6xc5 d4xc5 e6-e5) +1.14/10} a4
{(a5-a4 Qb3-b4 g6-g5 Bd3-c2 g5-g4 Bc2xa4 Ke8-e7 Ba4-c2 Rh8-h5 Bc2xf5 Rh5xf5
Kg2-g1 Ke7-f8) +0.63/15 39} 18. Qc2 {(Qb3-c2 e6-e5 Bd3xf5 g6xf5 Qc2xf5
e5-e4 h2-h4 Qc7-d7 Qf5xd7+ Ke8xd7 Ra1-b1 Kd7-e6) +0.71/9} Qc8 {(Qc7-c8
Be1-d2 e6-e5 d4xe5 Nf6-g4 Bd3xf5 g6xf5 f2-f4 Qc8-e6 h2-h3 Qe6-f6 e5xf6
Ng4xe3+) +0.36/15 47} 19. h4 {(h2-h4 Qc8-d7 Be1-b4) +1.45/10} Qd7 {(Qc8-d7
Be1-b4 O-O Rh1-e1 Qd7-c7 Kg2-f1 Rf8-e8 Kf1-g2 e6-e5 Bd3xf5 g6xf5 Qc2xf5
e5-e4 Ra1-c1 Ra8-d8 Kg2-f1) +0.22/16 54} 20. Rb1 {(Ra1-b1 e6-e5 d4xe5)
+1.66/10} O-O {(O-O b2-b4 a4xb3/ep Rb1xb3 Ra8-a7 Bd3xf5 g6xf5 Kg2-f3)
0.00/16 31} 21. Qe2 {(Qc2-e2 Nf5-h6 f2-f3) +1.76/11} Nh6 {(Nf5-h6 f2-f3
Rf8-e8 b2-b4 a4xb3/ep Rb1xb3 Qd7-c8 g3-g4 e6-e5 g4-g5 e5xd4 g5xh6 Re8xe3
Qe2-b2 Qc8-e6 Be1-g3 g7xh6 Qb2xd4) -0.43/16 28} 22. f3 {(f2-f3 Ra8-a6)
+1.64/11} Rfe8 {(Rf8-e8 b2-b4 e6-e5 d4xe5 Re8xe5 Be1-c3 Re5-e6 g3-g4 Ra8-e8
Bc3-d4 Qd7-c7 h4-h5 g6-g5 Rh1-d1 Re6xe3 Bd4xe3 Qc7-g3+ Kg2xg3 Nf6xh5+
g4xh5) -0.62/17 44} 23. Bc3 {(Be1-c3 Qd7-c7 g3-g4 Nf6-d7 Rb1-e1 e6-e5 d4xe5
Nd7xc5 Bd3-c2 Nc5-d7 e3-e4 Nd7xe5 e4xd5) +1.89/11} Qc7 {(Qd7-c7 g3-g4 e6-e5
d4xe5 Nf6-d7 h4-h5 g6-g5 Bd3-c2 Nd7xc5 Rh1-d1 Re8-e6 Bc3-d4 b7-b6 Kg2-f2
Ra8-e8 Rb1-c1 Qc7-b8 Qe2-d2 Qb8-c7 Bd4xc5 b6xc5 Bc2xa4 Qc7xe5) -0.46/17 27}
24. g4 {(g3-g4 Nf6xg4 f3xg4) +1.99/9 0} Nd7 {(Nf6-d7 f3-f4 f7-f5 g4-g5
Nh6-g4 h4-h5 g6xh5 Rh1xh5 Kg8-f7) -1.60/11 0} 25. f4 {(f3-f4 f7-f5 g4-g5)
+1.49/9 0} f5 {(f7-f5 g4-g5 Nh6-g4) -1.73/12 0} 26. g5 {(g4-g5 Nh6-g4
h4-h5) +2.06/13 0} Ng4 {(Nh6-g4 h4-h5 g6xh5 Rh1xh5 Kg8-f7 Rb1-h1 Re8-g8
Rh5-h4 g7-g6 Rh4xg4 f5xg4 Qe2xg4 Rg8-g7 e3-e4 d5xe4 Bd3xe4) -2.00/13 0} 27.
h5 {(h4-h5 g6xh5 Rh1xh5 Kg8-f7 Rb1-h1 Re8-g8 Rh5-h4 g7-g6 Rh4xg4 f5xg4
Qe2xg4 Rg8-g7 Rh1-h6) +2.37/12 0} gxh5 {(g6xh5 Rh1xh5 Kg8-f7 Rb1-h1 Re8-g8
Rh5-h4 g7-g6 Rh4xg4 f5xg4 Qe2xg4 Rg8-g7 Rh1-h6 Ra8-f8 Qg4-h4) -2.18/12 0}
28. Rxh5 {(Rh1xh5 g7-g6 Rh5-h4 Kg8-g7 Rh4xg4 f5xg4 Qe2xg4 Re8-e7 Rb1-h1
Ra8-h8 Rh1xh8 Kg7xh8 Bd3xg6 Nd7-f8 Bg6-d3 Kh8-g8) +2.56/13 0} g6 {(g7-g6
Rh5-h4 Kg8-g7 Rh4xg4 f5xg4 Qe2xg4 Re8-e7 Rb1-h1 Ra8-h8 Rh1xh8 Kg7xh8 Bd3xg6
Nd7-f8 Qg4-h5+ Kh8-g8) -2.20/13 0} 29. Rh4 {(Rh5-h4 Kg8-g7 Rh4xg4 f5xg4
Qe2xg4 Re8-h8 Bd3xg6 Nd7-f8 Bg6-c2 Qc7-f7 Bc3-e1 Nf8-g6 b2-b3 a4xb3 Rb1xb3
Ng6-e7 Rb3xb7) +1.72/12 0} Kg7 {(Kg8-g7 Rb1-h1 Re8-h8 Qe2-e1 Ra8-g8 Kg2-f3
b7-b5 c5xb6/ep Qc7xb6 Rh1-h3 Qb6-b8 Qe1-h1 Rh8xh4 Rh3xh4 Nd7-e5+ f4xe5
Qb8xe5 d4xe5 Rg8-h8) -1.56/17 26} 30. Rxg4 {(Rh4xg4 f5xg4 Qe2xg4 Re8-h8
Bd3xg6 Nd7-f8 Bg6-h5 Qc7-d7 Rb1-h1 Nf8-g6 Bc3-e1 Qd7-f7 Be1-g3 Qf7-f5
Qg4xf5 e6xf5 Bg3-e1) +1.59/12 0} fxg4 {(f5xg4 Qe2xg4 Nd7-f8 Rb1-h1 Qc7-f7
Qg4-d1 Qf7-g8 Bd3-c2 Kg7-f7 Bc2xa4 Re8-b8 Qd1-b3 Kf7-e8 Kg2-f2 Ra8xa4
Qb3xa4 Qg8-h7 Rh1xh7) -1.06/16 6} 31. Qxg4 {(Qe2xg4 Re8-h8 Qg4xe6 Nd7-f8
Qe6-f6+ Kg7-g8 Bd3xg6 Nf8xg6 Qf6xg6+ Qc7-g7 Qg6-e6+ Qg7-f7 Qe6xf7+ Kg8xf7
Rb1-e1 Kf7-g6 e3-e4 d5xe4 Re1xe4) +1.44/11 0} Nf8 {(Nd7-f8 Rb1-h1 Qc7-f7
Rh1-h6 Re8-d8 e3-e4 Qf7-c7 Qg4-h4 Rd8-c8 e4xd5 e6xd5 Rh6-h8 Kg7-f7 Qh4-h6
Qc7xf4 Bd3xg6+ Kf7-e6 Bg6-c2+ Nf8-g6 Qh6xg6+ Qf4-f6 g5xf6) -1.21/17 29} 32.
Rh1 {(Rb1-h1 Qc7-f7 Rh1-h6 Kg7-g8 Qg4-h3 Qf7-g7 Rh6-h4 Re8-e7 Bc3-b4 Re7-f7
Bb4-c3) +3.28/10 0} Qf7 {(Qc7-f7 Rh1-h6 Re8-e7 Qg4-h3 Qf7-g8 Kg2-f2 Kg7-f7
Kf2-e2 Re7-d7 Rh6-h8 Qg8-g7 Bc3-e1 Rd7-d8 Ke2-d2 Kf7-e7 Qh3-f5 g6xf5
Rh8xf8) -1.17/17 17} 33. Qh3 {(Qg4-h3 Qf7-g8 e3-e4 Kg7-f7 Qh3-g3 Re8-e7
e4xd5 e6xd5 f4-f5 g6xf5 Rh1-h6 Ra8-e8 Bd3xf5) +3.12/10 0} Qg8 {(Qf7-g8
e3-e4 Kg7-f7 e4xd5 c6xd5 Qh3-e3 Qg8-g7 Qe3-e2 Kf7-e7 Bd3-b5 Re8-c8 Qe2-c2
Qg7-f7 Rh1-h4 b7-b6 c5xb6) -0.80/16 7} 34. Qg3 {(Qh3-g3 Kg7-f7 Rh1-h6
Qg8-g7 Qg3-h3 Kf7-e7 Rh6-h8 Qg7-f7 Bc3-b4) +3.27/12 0} Kf7 {(Kg7-f7 Rh1-h6
Re8-d8 Qg3-h3 Kf7-e7 Kg2-f2 Rd8-c8 Bd3xg6 Nf8xg6 Qh3xe6+ Ke7xe6 Rh6-h8
Qg8xh8 Kf2-e2 Ke6-f7 Ke2-d2) -0.56/18 21} 35. Rh6 {(Rh1-h6 Qg8-g7 Qg3-h3
Kf7-g8 Kg2-f1 Re8-e7 Kf1-e2 Ra8-e8 Rh6-h4 Re8-a8 Bc3-d2 Re7-f7) +3.09/11 0}
Reb8 {(Re8-b8 Qg3-h4 Kf7-e8 Qh4-e1 Ra8-a7 Bc3-a5 Qg8-f7 Qe1-b4 Rb8-a8
Ba5-b6 Qf7-e7 Bb6xa7 Qe7xc5 d4xc5 b7-b5) -0.74/17 23} 36. Qh2 {(Qg3-h2
Qg8-g7 Rh6-h8 Rb8-d8 Bc3-b4 Rd8-e8 Bd3-c2 Ra8-c8) +3.59/10 0} Ke8 {(Kf7-e8
Kg2-f1 Ke8-d7 Qh2-c2 Qg8-f7 Bd3xg6 Nf8xg6 Qc2xg6 Qf7xg6 Kf1-e2 Rb8-g8
Rh6-h7+ Qg6xh7 Ke2-d2 b7-b5 c5xb6/ep Kd7-c8 b6-b7+ Qh7xb7) -0.60/17 25} 37.
e4 {(e3-e4 d5xe4 Bd3xe4 Ke8-d7 Rh6-h8 Qg8-f7 f4-f5 e6xf5 Qh2-d6+ Kd7-e8
Qd6-e5+ Ke8-d7) +4.29/10 0} dxe4 {(d5xe4 Bd3xe4 Rb8-d8 Be4-d3 Ke8-d7 d4-d5
c6xd5 Bc3-f6 Kd7-c6 Bf6xd8 Ra8xd8 Bd3-c2 Kc6-b5 Qh2-g1 Qg8-g7 Qg1-e3 Qg7xb2
Qe3-b3+ a4xb3 a3-a4+) -0.33/18 28} 38. Rh8 {(Rh6-h8 Qg8-f7 Bd3xe4 Rb8-d8
Be4-f3 Rd8-d7 Kg2-g3 Ra8-d8 Bf3-e4 Ke8-e7) +3.31/10 0} Qf7 {(Qg8-f7 Bd3xe4
Rb8-c8 Kg2-g1 Rc8-d8 Qh2-e2 Qf7xf4 Be4xc6+ Ke8-e7 Bc6xb7 Ra8-b8 c5-c6)
-0.36/18 30} 39. Bxe4 {(Bd3xe4 Ke8-d7 f4-f5) +3.16/11 0} Rc8 {(Rb8-c8 d4-d5
c6xd5 Be4-d3 d5-d4 Qh2-h6 e6-e5 Bd3xg6 Qf7xg6 Rh8xf8+ Ke8-d7 Qh6xg6 Ra8-a6
f4xe5) -1.11/18 220} 40. Bf3 {(Be4-f3 Rc8-d8 Kg2-g3) +3.76/10 0} Rd8
{(Rc8-d8 Kg2-g1 Qf7-f5 Bf3-d1 Ke8-d7 Bd1-c2 Qf5-d5 Qh2-e2 Kd7-c8 Rh8xf8
Rd8xf8 Qe2-e5) -0.01/16 12} 41. d5 {(d4-d5 Rd8xd5 Bf3xd5) +3.70/10 0} Rxd5
{(Rd8xd5 Qh2-h6 Rd5-f5 Bc3-g7 Ke8-e7 Bg7xf8+ Ra8xf8 Rh8-h7 Rf5xg5+ Qh6xg5+
Ke7-d7 Rh7xf7+ Kd7-c8) -0.81/15 22} 42. Bxd5 {(Bf3xd5 e6xd5 Qh2-h6)
+2.94/11 0} exd5 {(e6xd5 Qh2-h3 Qf7-e7 Bc3-e5 Ke8-f7 Qh3-c3 Ra8-d8 Kg2-f2
Rd8-e8 Qc3-b4 Qe7-e6 Qb4xb7+ Nf8-d7 Rh8-h7+ Kf7-f8 Qb7xd7 Qe6-g4 Qd7xg4)
-0.93/17 12} 43. Qh6 {(Qh2-h6 Qf7-f5 Bc3-e5) +2.98/10 0} Qf5 {(Qf7-f5
Rh8xf8+ Qf5xf8 Qh6xg6+ Qf8-f7 Qg6-h6 Qf7xf4 Qh6-h8+ Ke8-d7 Qh8-h7+ Kd7-e8
Qh7-h5+ Ke8-d7 Qh5-h7+ Kd7-e8 Qh7-h5+ Ke8-d7 Qh5-h7+ Kd7-e8) -0.06/16 13}
44. Kg3 {(Kg2-g3 Ra8-d8 Bc3-f6) +2.74/11 0} Qd3+ {(Qf5-d3+ Kg3-h4 Qd3-f5
Bc3-e5 Ra8-d8 Kh4-g3 Qf5-d3+ Kg3-h4 Qd3-f5 Kh4-g3 Qf5-d3+ Kg3-h4 Qd3-f5
Kh4-g3) 0.00/15 3} 45. Kh4 {(Kg3-h4 Qd3-f5 Rh8xf8+) +2.16/13 0} Qf5
{(Qd3-f5 Rh8xf8+ Qf5xf8 Qh6xg6+ Ke8-d7 Bc3-f6 Ra8-e8 Qg6-h7+ Kd7-c8 Qh7-f5+
Kc8-c7 Bf6-e5+ Kc7-d8 Be5-f6+ Kd8-c7 Bf6-e5+ Kc7-d8 Be5-f6+ Kd8-c7 Bf6-e5+)
-0.07/16 7} 46. Rxf8+ {(Rh8xf8+ Qf5xf8 Qh6xg6+) +2.47/13 0} Qxf8 {(Qf5xf8
Qh6xg6+ Ke8-d7 Qg6-h7+ Qf8-e7 Qh7xe7+ Kd7xe7 f4-f5 Ra8-e8 g5-g6 Ke7-f8
f5-f6 d5-d4 Bc3-d2 Re8-e7) -0.82/18 22} 47. Qxg6+ {(Qh6xg6+ Qf8-f7 Qg6-d6
Qf7-e7 Bc3-f6 Qe7xd6 c5xd6 Ke8-d7 g5-g6 Kd7xd6 f4-f5) +2.48/11 0} Kd7
{(Ke8-d7 Qg6-h7+ Qf8-e7 Qh7xe7+ Kd7xe7 f4-f5 Ra8-f8 Kh4-g4 Rf8-e8 g5-g6
Ke7-f8 f5-f6 d5-d4 Bc3-d2 Kf8-g8 f6-f7+ Kg8-g7 f7xe8Q Kg7-f6) -1.62/19 15}
48. Bf6 {(Bc3-f6 Kd7-c7 Qg6-h7+) +3.54/10 0} Re8 {(Ra8-e8 Qg6-h7+ Kd7-c8
Qh7-f5+ Kc8-c7 Bf6-e5+ Kc7-d8 Be5-f6+ Kd8-c7 Bf6-e5+ Kc7-d8 Be5-f6+ Kd8-c7
Bf6-e5+) -0.02/17 5} 49. Qh7+ {(Qg6-h7+ Kd7-c8 Qh7-f5+ Kc8-c7 Bf6-e5+
Kc7-d8 Qf5xf8 Re8xf8 g5-g6 Kd8-e7 Be5-d6+ Ke7-e8 Bd6xf8 Ke8xf8 f4-f5 d5-d4
Kh4-g3 d4-d3 Kg3-f3 Kf8-g7) +4.64/13 0} Kc8 {(Kd7-c8 Qh7-f5+ Kc8-c7 Bf6-e5+
Kc7-d8 Qf5xf8 Re8xf8 g5-g6 d5-d4 g6-g7 Rf8-e8 Be5xd4 Kd8-e7 f4-f5 Ke7-f7
Kh4-g5 Re8-e4 Bd4-c3 Re4-c4 f5-f6 Rc4xc5+ Kg5-f4 Kf7-g8) -0.62/18 3} 50.
Qf5+ {(Qh7-f5+ Kc8-c7 Bf6-e5+ Kc7-d8 Qf5xf8 Re8xf8 g5-g6 d5-d4 Be5xd4
Rf8xf4+ Kh4-g5 Rf4xd4 g6-g7 Kd8-d7 g7-g8Q Rd4-d5+ Kg5-f6) +4.79/13 0} Kb8
{(Kc8-b8 Bf6-e5+ Kb8-a8 Qf5-c2 Re8xe5 f4xe5 Qf8-f4+ Kh4-h5 Qf4-e4 Qc2xe4
d5xe4) -1.05/19 17} 51. Be5+ {(Bf6-e5+ Kb8-a7 Qf5xf8 Re8xf8 g5-g6 d5-d4
g6-g7 Rf8-d8 Be5-f6 Rd8-g8 Bf6xd4 Ka7-a6 Kh4-g5 Rg8-e8) +6.63/12 0} Ka8
{(Kb8-a8 Qf5-c2 Re8xe5 f4xe5 Ka8-b8 Qc2xa4) -3.37/19 26} 52. Qxf8 {(Qf5xf8
Re8xf8 g5-g6 Rf8-d8 Be5-f6 Rd8-g8 f4-f5 Ka8-a7 g6-g7 b7-b6 Kh4-g5 b6xc5
Bf6-e5 Ka7-b7 f5-f6 Kb7-a7) +7.40/14 0} Rxf8 {(Re8xf8 g5-g6 Rf8-e8 g6-g7
Ka8-a7 Kh4-g5 b7-b5 Kg5-g6 Ka7-a8 Kg6-f7 Ka8-a7) -7.24/23 12} 53. g6
{(g5-g6 Rf8-d8 Be5-f6 Rd8-g8 f4-f5 Ka8-b8 g6-g7 d5-d4 Bf6xd4 Kb8-c8 Kh4-g5
Kc8-d7 Kg5-g6) +7.45/12 0} Ka7 {(Ka8-a7 g6-g7 Rf8-d8 f4-f5 d5-d4 Be5-f6
Rd8-d5 g7-g8Q Rd5xf5 Qg8-d8 d4-d3 Qd8-d4 Rf5-d5 Qd4xa4+ Ka7-b8 Bf6-e5+
Kb8-c8 Qa4-a8+ Kc8-d7 Qa8-d8+ Kd7xd8 Kh4-g3 Rd5xe5) -6.45/20 9} 54. g7
{(g6-g7 Rf8-d8 Be5-f6 Rd8-g8 f4-f5 b7-b5 Bf6-e5 d5-d4 Be5xd4 Rg8-d8 Bd4-e5)
+7.98/11 0} Re8 {(Rf8-e8 Kh4-g3 Ka7-a6 f4-f5 Re8xe5 g7-g8Q Ka6-a7 f5-f6
Re5-f5 f6-f7 b7-b5 f7-f8Q Rf5xf8 Qg8xf8 Ka7-b7) -8.49/21 20} 55. Kg5
{(Kh4-g5 b7-b6 f4-f5 b6xc5 Kg5-g6 Re8xe5 g7-g8Q Re5-e2 Qg8-c8 Re2-g2+
Kg6-f7 Rg2xb2) +8.37/10 0} Ka6 {(Ka7-a6 f4-f5 Re8xe5 g7-g8Q Ka6-a7 Kg5-f4
Re5-e4+ Kf4-f3 Re4-e5 Qg8-g4 d5-d4 f5-f6 Re5-d5 f6-f7 Rd5-d8 Qg4-f4 d4-d3
Qf4-h4 Rd8-f8 Qh4xa4+ Ka7-b8) -8.43/19 8} 56. Kg6 {(Kg5-g6 Ka6-b5 f4-f5
Re8xe5 g7-g8Q Re5-e1 Qg8-c8 Re1-g1+ Kg6-h6 Kb5xc5 f5-f6 Rg1-f1) +8.16/10 0}
Kb5 {(Ka6-b5 Kg6-f7 Re8-d8 g7-g8Q Rd8xg8 Kf7xg8 Kb5xc5 f4-f5 d5-d4 f5-f6
Kc5-d5 Be5-f4 Kd5-e4 Bf4-h6 Ke4-d3 f6-f7 Kd3-c2 Kg8-g7 Kc2xb2) -8.34/17 3}
57. Kf7 {(Kg6-f7 Re8-a8 g7-g8Q Ra8xg8 Kf7xg8 Kb5-c4 f4-f5 Kc4xc5 f5-f6
d5-d4 Be5-f4 Kc5-c4 f6-f7) +9.58/11 0} Ra8 {(Re8-a8 g7-g8Q Ra8xg8 Kf7xg8
Kb5xc5 f4-f5 Kc5-c4 f5-f6 Kc4-d3 f6-f7 Kd3-e4 Be5-g7 d5-d4 Bg7-h6 Ke4-d3
f7-f8Q Kd3-c2 Qf8-f2+ Kc2-d3) -9.78/22 11} 58. g8=Q {(g7-g8Q Ra8xg8 Kf7xg8
Kb5xc5 f4-f5 b7-b5 f5-f6 d5-d4 f6-f7 Kc5-d5 f7-f8Q) +9.99/10 0} Rxg8
{(Ra8xg8 Kf7xg8 Kb5xc5 f4-f5 d5-d4 f5-f6 Kc5-c4 f6-f7 Kc4-b3 f7-f8Q Kb3xb2)
-10.35/23 10} 59. Kxg8 {(Kf7xg8 Kb5xc5 f4-f5 d5-d4 f5-f6 d4-d3 Be5-f4 d3-d2
Bf4xd2 Kc5-c4 Kg8-h8 Kc4-b3) +9.09/10 0} Kxc5 {(Kb5xc5 f4-f5 d5-d4 f5-f6
Kc5-d5 Be5-c7 c6-c5 f6-f7 Kd5-e6 f7-f8Q c5-c4 Qf8-d6+ Ke6-f5 Qd6-d5+ Kf5-g6
Qd5xd4 c4-c3 Qd4xa4 b7-b6) -10.48/21 10} 60. f5 {(f4-f5 d5-d4 f5-f6 Kc5-d5
Be5xd4 c6-c5 f6-f7 c5xd4 f7-f8Q Kd5-e4 Qf8-e8+ Ke4-d5 Qe8-e1) +10.27/11 0}
d4 {(d5-d4 f5-f6 Kc5-d5 Be5-c7 c6-c5 f6-f7 Kd5-c6 f7-f8Q Kc6xc7 Qf8xc5+
Kc7-d7 Qc5-c6+ b7xc6 b2-b4 a4xb3/ep a3-a4) -10.95/19 8} 61. f6 {(f5-f6
Kc5-d5 Be5xd4 Kd5xd4 f6-f7 c6-c5 f7-f8Q b7-b5 Qf8-d6+ Kd4-c4 Qd6-c6 b5-b4
Qc6xa4 Kc4-d5 Qa4-a8+ Kd5-d4) +10.42/10 0} Kd5 {(Kc5-d5 Be5-c7 Kd5-c4 f6-f7
Kc4-b3 f7-f8Q d4-d3 Qf8-b4+ Kb3-a2 Qb4xa4 c6-c5 Qa4-c4+ Ka2-a1 b2-b3)
-10.89/16 5 Black resigns} *[/pgn]

[Fritz 0]

Dragon at 2805 Elo should move instantly. You are doing something wrong if it takes 2-3 seconds per move.

[Chessqueen]

Dragon at 2805 Elo should move instantly. You are doing something wrong if it takes 2-3 seconds per move.

Whenever you set Komodo Dragon Elo = to whatever , most of the times it moves every second, but at certain point it takes 2 to 3 seconds, therefore, I only post the maximum amount of time. Anybody here on this forum can take a chronometer and measure how many seconds it take for Komodo Dragon to move, as average I would say 2 seconds. I noticed that when Komodo Dragon time control is down to 20 seconds, it moves instantly, like a fraction of a second per move specially during the endgame

Note: in Most game regardless of the T/C that you give to the opponent engine Komodo Dragon for the entire game only take around 60 to 100 seconds depending how many moves. There was a game with 257 moves that it took Komodo Dragon only around 4 minutes to finish the entire game and Shredder8 the entire T/C of 15/10 which is about 17 minutes total with only 10 seconds left on the clock when they both reached a draw position. Before you make any comments why don't you set Komodo Dragon Elo = whatever against another engine and since most of the time Komodo Dragon does not predict the opponent next move it will take at least 1 to 2 seconds to respond, whereas, if it is Komodo Dragon playing versus itself then the moves are played within fraction of a seconds since Dragon already knows the best answer according to the calculation done by the same engine

[lkaufman]

Dragon at 2805 Elo should move instantly. You are doing something wrong if it takes 2-3 seconds per move.

Whenever you set Komodo Dragon Elo = to whatever , most of the times it moves every second, but at certain point it takes 2 to 3 seconds, therefore, I only post the maximum amount of time. Anybody here on this forum can take a chronometer and measure how many seconds it take for Komodo Dragon to move, as average I would say 2 seconds. I noticed that when Komodo Dragon time control is down to 20 seconds, it moves instantly, like a fraction of a second per move specially during the endgame

Note: in Most game regardless of the T/C that you give to the opponent engine Komodo Dragon for the entire game only take around 60 to 100 seconds depending how many moves. There was a game with 257 moves that it took Komodo Dragon only around 4 minutes to finish the entire game and Shredder8 the entire T/C of 15/10 which is about 17 minutes total with only 10 seconds left on the clock when they both reached a draw position. Before you make any comments why don't you set Komodo Dragon Elo = whatever against another engine and since most of the time Komodo Dragon does not predict the opponent next move it will take at least 1 to 2 seconds to respond, whereas, if it is Komodo Dragon playing versus itself then the moves are played within fraction of a seconds since Dragon already knows the best answer according to the calculation done by the same engine

I have to agree with "Fritz 0" here; with a setting of Elo 2805 (or anywhere in the human range), Komodo Dragon (any version with Elo settings) should move "instantly", meaning in less than a tenth of a second, and I confirmed this on my own laptop with a quick game against it myself. I used the Fritz GUI, and it never took any time detectible to me for any move, so my guess is that there is some issue with the specific GUI you are using or else with the computer you are using. It should never take anywhere near even one second for any move under these conditions. This is with Threads = 1. If you used many threads, it would take more time, but still should be under half a second per move consistently. There were some issues with certain GUIs not handling the Elo properly in 2.6.1 so we reverted to the 2.6 method in Dragon 3, but apparently it is using the Elo or else it would take similar time to the opponent. In test games with GM Lenderman, with a setting of 2600 it averaged only about a quarter of a second per GAME (not move!); at 2800 it might be about one second per GAME. But each GUI has its own overhead so it won't be this fast on all GUIs.

[Chessqueen]

Dragon at 2805 Elo should move instantly. You are doing something wrong if it takes 2-3 seconds per move.

Whenever you set Komodo Dragon Elo = to whatever , most of the times it moves every second, but at certain point it takes 2 to 3 seconds, therefore, I only post the maximum amount of time. Anybody here on this forum can take a chronometer and measure how many seconds it take for Komodo Dragon to move, as average I would say 2 seconds. I noticed that when Komodo Dragon time control is down to 20 seconds, it moves instantly, like a fraction of a second per move specially during the endgame

Note: in Most game regardless of the T/C that you give to the opponent engine Komodo Dragon for the entire game only take around 60 to 100 seconds depending how many moves. There was a game with 257 moves that it took Komodo Dragon only around 4 minutes to finish the entire game and Shredder8 the entire T/C of 15/10 which is about 17 minutes total with only 10 seconds left on the clock when they both reached a draw position. Before you make any comments why don't you set Komodo Dragon Elo = whatever against another engine and since most of the time Komodo Dragon does not predict the opponent next move it will take at least 1 to 2 seconds to respond, whereas, if it is Komodo Dragon playing versus itself then the moves are played within fraction of a seconds since Dragon already knows the best answer according to the calculation done by the same engine

I have to agree with "Fritz 0" here; with a setting of Elo 2805 (or anywhere in the human range), Komodo Dragon (any version with Elo settings) should move "instantly", meaning in less than a tenth of a second, and I confirmed this on my own laptop with a quick game against it myself. I used the Fritz GUI, and it never took any time detectible to me for any move, so my guess is that there is some issue with the specific GUI you are using or else with the computer you are using. It should never take anywhere near even one second for any move under these conditions. This is with Threads = 1. If you used many threads, it would take more time, but still should be under half a second per move consistently. There were some issues with certain GUIs not handling the Elo properly in 2.6.1 so we reverted to the 2.6 method in Dragon 3, but apparently it is using the Elo or else it would take similar time to the opponent. In test games with GM Lenderman, with a setting of 2600 it averaged only about a quarter of a second per GAME (not move!); at 2800 it might be about one second per GAME. But each GUI has its own overhead so it won't be this fast on all GUIs.

I was using Arena 3.5.1 Gui, when I switched to Shredder GUI it move instantly in less than a tenth of a second

[BrendanJNorman]

Dragon at 2805 Elo should move instantly. You are doing something wrong if it takes 2-3 seconds per move.

Whenever you set Komodo Dragon Elo = to whatever , most of the times it moves every second, but at certain point it takes 2 to 3 seconds, therefore, I only post the maximum amount of time. Anybody here on this forum can take a chronometer and measure how many seconds it take for Komodo Dragon to move, as average I would say 2 seconds. I noticed that when Komodo Dragon time control is down to 20 seconds, it moves instantly, like a fraction of a second per move specially during the endgame

Note: in Most game regardless of the T/C that you give to the opponent engine Komodo Dragon for the entire game only take around 60 to 100 seconds depending how many moves. There was a game with 257 moves that it took Komodo Dragon only around 4 minutes to finish the entire game and Shredder8 the entire T/C of 15/10 which is about 17 minutes total with only 10 seconds left on the clock when they both reached a draw position. Before you make any comments why don't you set Komodo Dragon Elo = whatever against another engine and since most of the time Komodo Dragon does not predict the opponent next move it will take at least 1 to 2 seconds to respond, whereas, if it is Komodo Dragon playing versus itself then the moves are played within fraction of a seconds since Dragon already knows the best answer according to the calculation done by the same engine

I have to agree with "Fritz 0" here; with a setting of Elo 2805 (or anywhere in the human range), Komodo Dragon (any version with Elo settings) should move "instantly", meaning in less than a tenth of a second, and I confirmed this on my own laptop with a quick game against it myself. I used the Fritz GUI, and it never took any time detectible to me for any move, so my guess is that there is some issue with the specific GUI you are using or else with the computer you are using. It should never take anywhere near even one second for any move under these conditions. This is with Threads = 1. If you used many threads, it would take more time, but still should be under half a second per move consistently. There were some issues with certain GUIs not handling the Elo properly in 2.6.1 so we reverted to the 2.6 method in Dragon 3, but apparently it is using the Elo or else it would take similar time to the opponent. In test games with GM Lenderman, with a setting of 2600 it averaged only about a quarter of a second per GAME (not move!); at 2800 it might be about one second per GAME. But each GUI has its own overhead so it won't be this fast on all GUIs.

Any plans to introduce a UCI_Sleep feature in future versions similar to what MByrne did with Honey?

The idea is to make it "sleep" for a variable time before moving when on weakened settings to avoid the jarring (and very unrealistic for training) insta-response every time you move against it.

[Fritz 0]

Dragon at 2805 Elo should move instantly. You are doing something wrong if it takes 2-3 seconds per move.

Whenever you set Komodo Dragon Elo = to whatever , most of the times it moves every second, but at certain point it takes 2 to 3 seconds, therefore, I only post the maximum amount of time. Anybody here on this forum can take a chronometer and measure how many seconds it take for Komodo Dragon to move, as average I would say 2 seconds. I noticed that when Komodo Dragon time control is down to 20 seconds, it moves instantly, like a fraction of a second per move specially during the endgame

Note: in Most game regardless of the T/C that you give to the opponent engine Komodo Dragon for the entire game only take around 60 to 100 seconds depending how many moves. There was a game with 257 moves that it took Komodo Dragon only around 4 minutes to finish the entire game and Shredder8 the entire T/C of 15/10 which is about 17 minutes total with only 10 seconds left on the clock when they both reached a draw position. Before you make any comments why don't you set Komodo Dragon Elo = whatever against another engine and since most of the time Komodo Dragon does not predict the opponent next move it will take at least 1 to 2 seconds to respond, whereas, if it is Komodo Dragon playing versus itself then the moves are played within fraction of a seconds since Dragon already knows the best answer according to the calculation done by the same engine

I have to agree with "Fritz 0" here; with a setting of Elo 2805 (or anywhere in the human range), Komodo Dragon (any version with Elo settings) should move "instantly", meaning in less than a tenth of a second, and I confirmed this on my own laptop with a quick game against it myself. I used the Fritz GUI, and it never took any time detectible to me for any move, so my guess is that there is some issue with the specific GUI you are using or else with the computer you are using. It should never take anywhere near even one second for any move under these conditions. This is with Threads = 1. If you used many threads, it would take more time, but still should be under half a second per move consistently. There were some issues with certain GUIs not handling the Elo properly in 2.6.1 so we reverted to the 2.6 method in Dragon 3, but apparently it is using the Elo or else it would take similar time to the opponent. In test games with GM Lenderman, with a setting of 2600 it averaged only about a quarter of a second per GAME (not move!); at 2800 it might be about one second per GAME. But each GUI has its own overhead so it won't be this fast on all GUIs.

Any plans to introduce a UCI_Sleep feature in future versions similar to what MByrne did with Honey?

The idea is to make it "sleep" for a variable time before moving when on weakened settings to avoid the jarring (and very unrealistic for training) insta-response every time you move against it.

Wouldn't that give the human pondering time and make Dragon relatively weaker than intended at a certain Elo setting?

[BrendanJNorman]

Dragon at 2805 Elo should move instantly. You are doing something wrong if it takes 2-3 seconds per move.

Whenever you set Komodo Dragon Elo = to whatever , most of the times it moves every second, but at certain point it takes 2 to 3 seconds, therefore, I only post the maximum amount of time. Anybody here on this forum can take a chronometer and measure how many seconds it take for Komodo Dragon to move, as average I would say 2 seconds. I noticed that when Komodo Dragon time control is down to 20 seconds, it moves instantly, like a fraction of a second per move specially during the endgame

Note: in Most game regardless of the T/C that you give to the opponent engine Komodo Dragon for the entire game only take around 60 to 100 seconds depending how many moves. There was a game with 257 moves that it took Komodo Dragon only around 4 minutes to finish the entire game and Shredder8 the entire T/C of 15/10 which is about 17 minutes total with only 10 seconds left on the clock when they both reached a draw position. Before you make any comments why don't you set Komodo Dragon Elo = whatever against another engine and since most of the time Komodo Dragon does not predict the opponent next move it will take at least 1 to 2 seconds to respond, whereas, if it is Komodo Dragon playing versus itself then the moves are played within fraction of a seconds since Dragon already knows the best answer according to the calculation done by the same engine

I have to agree with "Fritz 0" here; with a setting of Elo 2805 (or anywhere in the human range), Komodo Dragon (any version with Elo settings) should move "instantly", meaning in less than a tenth of a second, and I confirmed this on my own laptop with a quick game against it myself. I used the Fritz GUI, and it never took any time detectible to me for any move, so my guess is that there is some issue with the specific GUI you are using or else with the computer you are using. It should never take anywhere near even one second for any move under these conditions. This is with Threads = 1. If you used many threads, it would take more time, but still should be under half a second per move consistently. There were some issues with certain GUIs not handling the Elo properly in 2.6.1 so we reverted to the 2.6 method in Dragon 3, but apparently it is using the Elo or else it would take similar time to the opponent. In test games with GM Lenderman, with a setting of 2600 it averaged only about a quarter of a second per GAME (not move!); at 2800 it might be about one second per GAME. But each GUI has its own overhead so it won't be this fast on all GUIs.

Any plans to introduce a UCI_Sleep feature in future versions similar to what MByrne did with Honey?

The idea is to make it "sleep" for a variable time before moving when on weakened settings to avoid the jarring (and very unrealistic for training) insta-response every time you move against it.

Wouldn't that give the human pondering time and make Dragon relatively weaker than intended at a certain Elo setting?

Does it matter? The human SHOULD have pondering time. Just as they do in a real game with a real opponent (which is what the bloody thing is supposed to be simulating!).

A real 2200 player as an example, isn't blitzing his moves out at breakneck speed.

So if Dragon is REALLY replicating a 2200 opponent, there should also be "pondering" time included.

[Fritz 0]

Dragon at 2805 Elo should move instantly. You are doing something wrong if it takes 2-3 seconds per move.

Whenever you set Komodo Dragon Elo = to whatever , most of the times it moves every second, but at certain point it takes 2 to 3 seconds, therefore, I only post the maximum amount of time. Anybody here on this forum can take a chronometer and measure how many seconds it take for Komodo Dragon to move, as average I would say 2 seconds. I noticed that when Komodo Dragon time control is down to 20 seconds, it moves instantly, like a fraction of a second per move specially during the endgame

Note: in Most game regardless of the T/C that you give to the opponent engine Komodo Dragon for the entire game only take around 60 to 100 seconds depending how many moves. There was a game with 257 moves that it took Komodo Dragon only around 4 minutes to finish the entire game and Shredder8 the entire T/C of 15/10 which is about 17 minutes total with only 10 seconds left on the clock when they both reached a draw position. Before you make any comments why don't you set Komodo Dragon Elo = whatever against another engine and since most of the time Komodo Dragon does not predict the opponent next move it will take at least 1 to 2 seconds to respond, whereas, if it is Komodo Dragon playing versus itself then the moves are played within fraction of a seconds since Dragon already knows the best answer according to the calculation done by the same engine

I have to agree with "Fritz 0" here; with a setting of Elo 2805 (or anywhere in the human range), Komodo Dragon (any version with Elo settings) should move "instantly", meaning in less than a tenth of a second, and I confirmed this on my own laptop with a quick game against it myself. I used the Fritz GUI, and it never took any time detectible to me for any move, so my guess is that there is some issue with the specific GUI you are using or else with the computer you are using. It should never take anywhere near even one second for any move under these conditions. This is with Threads = 1. If you used many threads, it would take more time, but still should be under half a second per move consistently. There were some issues with certain GUIs not handling the Elo properly in 2.6.1 so we reverted to the 2.6 method in Dragon 3, but apparently it is using the Elo or else it would take similar time to the opponent. In test games with GM Lenderman, with a setting of 2600 it averaged only about a quarter of a second per GAME (not move!); at 2800 it might be about one second per GAME. But each GUI has its own overhead so it won't be this fast on all GUIs.

Any plans to introduce a UCI_Sleep feature in future versions similar to what MByrne did with Honey?

The idea is to make it "sleep" for a variable time before moving when on weakened settings to avoid the jarring (and very unrealistic for training) insta-response every time you move against it.

Wouldn't that give the human pondering time and make Dragon relatively weaker than intended at a certain Elo setting?

Does it matter? The human SHOULD have pondering time. Just as they do in a real game with a real opponent (which is what the bloody thing is supposed to be simulating!).

A real 2200 player as an example, isn't blitzing his moves out at breakneck speed.

So if Dragon is REALLY replicating a 2200 opponent, there should also be "pondering" time included.

I am just saying that with included pondering time Dragon Elo values would have to be recalibrated.

Personally, I am not a fun of engines' artificial delay. I have better things to do with my time than to wait for the engine which is doing nothing.