-gomaxprocs and other CLI args do not work with fortio server

[amarjayr]

Running fortio server -gomaxprocs=16 does not have any affect on runtime.GOMAXPROCS.

The only place where runtime.GOMAXPROCS is set is fortio_main.go:357 which processes the fortio load command.

I'm happy to add a PR to either add a gomaxprocs field to the fortio server UI or have fortio server -gomaxprocs=16 parsed correctly on the CLI. Please advise which is preferable.

[ldemailly]

While in the golang that fortio builds are using it probably doesn't need to be changed from the default value (num cores), you are right @amarjayr. I think it can be moved to common part so it would apply to fortio server
I wonder if it would really need to be changeable per request

Side question: did you check what happens in k8s env, is the value related to request/limit or using the node's value?