cdani wrote:Rebel wrote:Nobody cares?
Or do I miss something?
Thanks for your investigations!
As I don't feel that I have a problem to solve, for the moment I keep doing like always, but this is noted for if something related seems to happen. Is like what Bob said of testing with Linux, very useful in some context.
The developers of Linux have invested much more attention in core scheduling than Microsoft, if it's better remains the question, see the WIKI -
Scheduling_(computing)
I have finished my first test with affinity and the results are dramatic. 8 cores, 8 matches, each match 'with its own core. I took a change good for +/-10 elo based on a previous testrun of 3 x 4800 games on 40/15, 40/30 and 40/60.
Code: Select all
CPU Result Perc Time ELO LOS
Normal 2485|4800 51.8% 40/15 +12 99.9%
Affinity 2455|4800 51.1% 40/15 +8 98.0%
0.7% less, alright can happen with just 4800 games.
Code: Select all
CPU Result Perc Time ELO LOS
Normal 2437|4800 50.8% 40/30 +5 92.2%
Affinity 2417|4800 50.4% 40/30 +3 74.7%
Another loss, still acceptable, but then the 40/60 run:
Code: Select all
CPU Result Perc Time ELO LOS
Normal 2470|4800 51.5% 40/60 +10 99.7%
Affinity 2369|4800 49.4% 40/60 -4 11.1%
A loss of 14 elo ???
I don't understand what's going on, it looked so good in theory. Anyway, I am going to try 2 other programs in order to see if this is something universal chronic or ProDeo related.
To be continued.