Chess2u
Would you like to react to this message? Create an account in a few clicks or log in to continue.

Chess2uLog in

descriptionAdequate time control for Blitz matches EmptyAdequate time control for Blitz matches

more_horiz
The purpose of this tread is to find the sweet spot range for playing many games and to try letting the error ratio stay relatively stable.

Candidates:

3min + 2sec - equivalent to 10min.

6min + 4sec - equivalent to 20 min.




Candidates number 2

4min +1sec

2min +3sec

descriptionAdequate time control for Blitz matches EmptyRe: Adequate time control for Blitz matches

more_horiz
Adequate time control for Blitz matches Laptop10

[pgn][Event "Expert-PC Laptop, Blitz 3m+3s"]
[Site "URAUEB-"]
[Date "2015.05.23"]
[Round "13"]
[White "Stockfish 210515 64"]
[Black "Komodo 9.01 64-bit"]
[Result "0-1"]
[ECO "D46"]
[Annotator "0.02;0.21"]
[PlyCount "120"]
[TimeControl "180+3"]

{AMD Athlon(tm) II P320 Dual-Core Processor 2094 MHz  W=23.5 plies; 2 161kN/s;
aMaLiA pOwEr.ctg  B=20.6 plies; 2 088kN/s; aMaLiA pOwEr.ctg} 1. d4 {B 0} d5 {
B 0} 2. c4 {B 0} c6 {B 0} 3. Nf3 {B 0} Nf6 {B 0} 4. Nc3 {B 0} e6 {B 0} 5. e3 {
B 0} Nbd7 {B 0} 6. Qc2 {B 0} Bd6 {B 0} 7. Bd3 {B 0} O-O {B 0} 8. O-O {B 0} dxc4
{B 0} 9. Bxc4 {B 0} b5 {B 0} 10. Be2 {B 0} Bb7 {B 0} 11. Rd1 {B 0} Qc7 {B 0}
12. e4 {B 0} e5 {B 0 Both last book move} 13. g3 {0.02/22 8} Rfe8 {0.21/18 15}
14. a3 {0.00/22 15 (Be3)} a6 {-0.10/18 13} 15. Be3 {-0.09/22 7 (Bg5)} Ng4 {-0.
10/18 5} 16. dxe5 {-0.05/19 1 (Bc1)} Nxe3 {-0.47/18 3 (Ndxe5)} 17. exd6 {-0.37/
23 8} Nxc2 {-0.45/20 5} 18. dxc7 {-0.47/20 1} Nxa1 {-0.18/21 5} 19. Rxd7 {-0.
29/25 8} Nb3 {-0.30/21 4} 20. Ng5 {-0.43/24 7 (Nd4)} Nc5 {-0.66/20 5} 21. Rxf7
{-0.45/20 1} Bc8 {-0.62/22 8 (Ne6)} 22. Rf3 {-0.73/22 11} h6 {-0.86/22 7} 23.
Nf7 {-0.96/25 9} Bg4 {-0.85/23 6 (Nxe4)} 24. Nd6 {-0.95/24 14} Bxf3 {-0.90/23 6
} 25. Bxf3 {-0.93/21 1} Rec8 {-1.03/22 9} 26. b4 {-0.99/24 11} Nd3 {-1.06/21 4
(Nd7)} 27. Nxc8 {-0.97/25 13} Rxc8 {-1.06/20 3} 28. Be2 {-1.05/21 2} Ne1 {-1.
13/21 9 (Ne5)} 29. Kf1 {-0.97/27 15 (e5)} Nc2 {-1.08/19 3} 30. Nb1 {-1.05/27 9}
Rxc7 {-1.05/20 6} 31. Bd1 {-1.03/23 3} c5 {-1.14/23 17 (Nd4)} 32. bxc5 {-1.00/
27 8} Rxc5 {-1.18/24 12} 33. Ke2 {-0.95/26 4} Nd4+ {-1.12/21 5} 34. Kd2 {-1.05/
26 7} Nc6 {-1.20/22 7} 35. Nc3 {-1.06/22 2 (Bb3+)} Na5 {-1.17/22 7 (Ne5)} 36.
Kd3 {-1.10/27 10} Kf8 {-1.15/22 8} 37. Be2 {-1.03/24 1} Rc6 {-1.19/23 10 (Rc8)}
38. Kc2 {-1.05/25 12} Nc4 {-1.23/22 5} 39. Bxc4 {-1.24/26 16} Rxc4 {-1.19/20 3}
40. Kd3 {-1.30/27 7} Rc8 {-1.25/20 4 (Kf7)} 41. f3 {-1.32/25 12 (f4)} Ke7 {-1.
47/21 10} 42. f4 {-1.38/28 26} Kd6 {-1.36/21 10 (Ke6)} 43. Kd4 {-1.38/27 4
(e5+)} Rc4+ {-1.96/18 3 (Ke6)} 44. Kd3 {-1.48/27 9} Kc5 {-2.08/19 4 (Rc5)} 45.
e5 {-1.83/24 5} Rd4+ {-2.17/21 10} 46. Ke3 {-1.83/23 1 (Kc2)} Kc4 {-2.54/18 3}
47. e6 {-2.68/25 16 (Ne2)} Rd3+ {-2.96/20 6} 48. Ke2 {-2.81/26 8} Rd8 {-3.03/
21 6} 49. Nb1 {-3.16/25 18} g6 {-3.16/21 5 (Kd5)} 50. Ke3 {-3.08/23 14 (g4)}
Rd3+ {-4.08/19 6 (Kd5)} 51. Kf2 {-3.82/23 6 (Ke4)} Rd6 {-4.47/21 4} 52. e7 {-4.
18/21 5} Re6 {-4.97/22 8} 53. Nd2+ {-3.93/20 1} Kc3 {-5.07/22 4 (Kd5)} 54. Nf3
{-4.59/21 6} Rxe7 {-5.24/19 3} 55. Ne5 {-5.24/22 4 (Nh4)} Re6 {-5.56/22 13} 56.
Nf7 {-5.49/20 3 (Kf3)} Kb3 {-6.09/20 5} 57. Nxh6 {-6.06/20 3} Kxa3 {-7.75/19 16
} 58. f5 {-7.43/19 3 (h4)} gxf5 {-9.84/18 5} 59. Nf7 {-9.76/23 4 (Nxf5)} b4 {
-10.71/19 4} 60. Ng5 {-10.30/21 3} Rc6 {-27.67/20 12 (b3)} 0-1

[/pgn]

descriptionAdequate time control for Blitz matches EmptyBullet Match 1+1

more_horiz
1 core each
Permanent brain enabled with the idea of in-directly increase total time each game.
128mb hash each - more than adequate with this relatively slow laptop.

Predicted move ratio = 62%  

Permanent brain wrote:
Pondering is less effective than normal thinking. For example, if the program guesses 25% of the opponent's moves correctly, the use of pondering is on average equivalent to increasing the normal calculating time by a factor of 1.25.


In this case the time factor is 1.62.

In chess games between two computers, pondering makes sense only if the competing chess engines use separate processors or cores. If they share the same core, the pondering program steals half of the time from the program thinking in the normal way and uses the stolen time less effectively.

Adequate time control for Blitz matches Bullet10

descriptionAdequate time control for Blitz matches EmptyRe: Adequate time control for Blitz matches

more_horiz
Permissions in this forum:
You cannot reply to topics in this forum