config: add --msPerBlock flag

[AliceInHunterland]

./runner.sh --nodes mixed --rpc sharp -d "Mytest" -m rate -q 50 -z 5m -t 30s --time $(TIME_PER_BLOCK)

example:

TARGETS := start.GoFourNodes10wrk start.GoFourNodes30wrk start.GoFourNodes100wrk
TIME_BLOCKS := 5000 1000 500 200 100

run-block-tests:
	@$(foreach target,$(TARGETS), \
		$(foreach time,$(TIME_BLOCKS), \
			echo "Running $(target) with time per block $(time) ms" && \
			$(MAKE) $(target) TIME_PER_BLOCK=$(time); \
		) \
	)

[AnnaShaleva]

The main question is: there are two steps during every benchmark run: the first is node configuration files generation from YAML templates, and the second is nodes start based on the generated configuration. MsPerBlock setting is added to both these steps. Have you ensured that these two settings are consistent? What happens if I'll specify different values at these two steps?

[AliceInHunterland]

The main question is: there are two steps during every benchmark run: the first is node configuration files generation from YAML templates, and the second is nodes start based on the generated configuration. MsPerBlock setting is added to both these steps. Have you ensured that these two settings are consistent? What happens if I'll specify different values at these two steps?

Before make prepare 1000
=> Stop environment
=> Generate configurations for single-node and four-nodes networks from templates
+ cd ./cmd
+ go run ./config/ --go-template go.protocol.template.yml --go-db leveldb --sharp-template sharp.protocol.template.yml --sharp-db LevelDBStore --msPerBlock 1000
creating: 1963633258/go.protocol.template.yml
creating: 1963633258/go.protocol.template.yml
creating: 1963633258/sharp.protocol.template.yml
creating: 1963633258/sharp.protocol.template.yml
After make prepare 1000

if you specify different value after make prepare directly in config files it will use your new value. so for running test it will use values from the last step.

[AnnaShaleva]

The logic itself LGTM, minor style fixes are left.