#Stockfish wierd output
32 messages · Page 1 of 1 (latest)
Perft count is correctly reported just above
319....
But this does show a weird output artifact that should be solved
sorry i forgot to mention, I want to see the nodes per second
You have the total nodes and the total seconds
oh :))))))
You can probably extract the ratio if you think hard enough about it
(you just need a division)
thx i didnt think about that
Np
Since you are presumably working on move generation , if you ever need to debug perft I suggest using webperft over SF
For any general engine dev question feel free to ask in #engines-dev
no, I already debugged my move generation, right now I just want to see how fast it is
Well if it's just purely to measure speed then sf is a good target
Are you also doing bulk counting?
Because sf does
thx, I might ask around if I stumble upon anything
So that inflates the final result by an order of magnitude
no, I want per position
That's a wrong answer
I saw if I use the default option it bulk counts them
yes
I think this is a regression
Bulk counting is a technique you can do if you have fully legal movegen
It lets you skip the last layer of make moves, it increases perft speed (but not actual search speed) by a factor of 10 or more
If you aren't doing it SF perft performance will appear very inflated compared to what you can get
ill search around, thanks for the insight
Yw
yeah, sf16 works fine but 16.1 doesn't