root@freebsd13-aa64:~ # fortio load -c 100 -n 1000000 -qps 0 http://127.0.0.1:8080/ http://127.0.0.1:8080/ Fortio dev running at 0 queries per second, --> 4->4

root@freebsd13-aa64:~ # fortio load -c 100 -n 1000000 -qps 0 http://127.0.0.1:8080/ http://127.0.0.1:8080/ Fortio dev running at 0 queries per second, --> 4->4 procs, <-- for 1000000 calls: http://127.0.0.1:8080/ http://127.0.0.1:8080/ 10:23:40 I httprunner.go:87> Starting http test for http://127.0.0.1:8080/ http://127.0.0.1:8080/ with 100 threads at -1.0 qps and parallel warmup Starting at max qps with 100 thread(s) --> [gomax 4] <-- for exactly 1000000 calls (10000 per thread + 0) caishu@ubuntu21-arm64:~$ fortio load -c 100 -n 1000000 -qps 0 http://localhost:8080/ http://localhost:8080/ Fortio 1.22.0 running at 0 queries per second, --> 2->2 procs <--, for 1000000 calls: http://localhost:8080/ http://localhost:8080/ 13:07:55 I httprunner.go:87> Starting http test for http://localhost:8080/ http://localhost:8080/ with 100 threads at -1.0 qps and parallel warmup Starting at max qps with 100 thread(s) --> [gomax 2] <-- for exactly 1000000 calls (10000 per thread + 0) Why half the GOMAXPROCS for the Linux example?