Maybe I was too stupid or not that involved in chess engine testing, but only after some small research in the source code of Stockfish 13 I figured out how to do the benchmark with more than one thread:

benchmark.cpp:

 95 /// setup_bench() builds a list of UCI commands to be run by bench. There
 96 /// are five parameters: TT size in MB, number of search threads that
 97 /// should be used, the limit value spent for each position, a file name
 98 /// where to look for positions in FEN format, the type of the limit:
 99 /// depth, perft, nodes and movetime (in millisecs), and evaluation type
100 /// mixed (default), classical, NNUE.
101 ///
102 /// bench -> search default positions up to depth 13
103 /// bench 64 1 15 -> search default positions up to depth 15 (TT = 64MB)
104 /// bench 64 4 5000 current movetime -> search current position with 4 threads for 5 sec
105 /// bench 64 1 100000 default nodes -> search default positions for 100K nodes each
106 /// bench 16 1 5 default perft -> run a perft 5 on default positions

bench 64 [Number of threads]

Update: A smart guy in the talkchess forum gave some advices, so I changed the settings. Surpressing the output and repeating the bench a few times should give more reliable results. I also deleted the lines with engines, where I wasn’t sure that these benchmarks are comparable. Though this test should actually only show where in the hardware ranking the M1 is located (roughly), my first try was probably too sloppy.

In addition I had some fun tonight digging up long forgotten knowledge. I built a small script running each bench ten times and calculating the average.

 1 #!/bin/zsh
 2 
 3 ########################################################
 4 # usage: bench.sh [engine] [number of threads]         #
 5 # for the Honey family:                                #
 6 # bench.sh [engine] [number of threads] 13 [true|false]#
 7 ########################################################
 8 
 9 test -e bench.tmp && rm bench.tmp
10 
11 i=0
12 
13 while [ $i -lt 10 ]; do
14     $1  bench 64 $2 $3 $4  1>/dev/null 2>>bench.tmp
15     let i=i+1
16 done
17 
18 test -e benchmarks/$2-threads-$1.txt && rm benchmarks/$2-threads-$1.txt
19 
20 grep 'second' bench.tmp | sed -e 's/.*[ \t]//'>>benchmarks/$2-threads-$1.txt
21 
22 sum=`cat benchmarks/$2-threads-$1.txt | awk '{sum+=$1} END{print sum}'`
23 
24 avg=$((sum / 10))
25 echo $avg
26 
27 rm bench.tmp
28

So here you go, the numbers are the nodes per second during the benchmark test:

*x86_64 binaries

For some engines I didn’t figure out yet how to do a multiple thread benchmark.