ppigazzini

I experimented a bit with `stockfish speedtest` as potential replacement of `stockfish bench` for the worker nps benchmark, but I didn't find a real difference in precision (ratio stdev /...

> * this will penalise SMP tests, where the actual nps will be higher than the one measured in this way. Could be solved by doing some SMP measurement for...

@vondele refactored to bench at different depths, print statistics, feel free to test with one of your workers adding test to DEV. Dual Xeon e5-2680v3: Click to view - test...

> So, some experiment on a 4 socket system is attached below. One setup where we have 1 worker per socket having concurrency 70 ('the normal one'), and one where...

Your worker at 70 cores completes the bench at depth 13 in 4.6s with threads=1 and 2.2s with threads=8, the relative std (to the average) is low with depth=13 and...

The worker at 280 core has a very bad `Std (%)` - SMP test at threads=8 ```yaml Statistic for stockfish_fa6c30af814fe91e6a6c2d1bcaa8d951e3724ae7_g++_13.3.0_env_25b32ad706: Concurrency : 35.00 Threads : 1.00 Depth : 13.00 Mean...

@Disservin @vondele in SMP tests `depht=13` has a better `Std (%)` wrt `depth=15` and in normal test the `Std (%)` is low even with worker at `concurrency=70`. IMO the PR...

> I think it still needs some testing to decide here. > > What I'm assuming is that it is actually the OS that has a bit of a problem...

I'm talking about fishtest with master. The difference is that with 10 worker@7, after a while, we are benching 1 worker while other 9 are running tests competing for the...

Triggered the workers update, thank you @Viren6 @jw1912 :)