blockbench: help in running benchmark/ethereum ssh timed out problem
@ijingo @ug93tad @dloghin there are some configurations set in file /benchmark/ethereum/hosts and benchmark/ethereum/clients,
when I run
./run-bench.sh 4 32 4 8
I always encounter the following output and I am not sure if it is an error which will prohibit the generation of the final results
ssh: connect to host 10.0.0.100 port 22: Operation timed out done node 10.0.0.100
I am wondering if I need to modify the contents in /benchmark/ethereum/hosts and /benchmark/ethereum/clients to fit the conditions of my own computer? If every user needs to modify them, then according to what guidance should we modify?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 17 (8 by maintainers)
@ballexaa - You could start some few VMs (e.g. if you have 8 cores in your system, start 8 VMs with one virtual core each). Update the content of
benchmark/hyperledger/clientsandbenchmark/hyperledger/hostswith the IP addresses of your VMs. For example, put 4 VMs as clients and 4 VMs as hosts.Make sure blockbench and hyperledger is installed on all VMs and that you have password-less access among the VMs (e.g. see https://www.linuxbabe.com/linux-server/setup-passwordless-ssh-login).
Go to
benchmark/hyperledgeron the VM that you want to act as master (e.g. the first one you have created) and setup the variables inenv.shaccording to your case (folders, etc.). Then run:You can also read more about these script in the readme from
benchmark/hyperledger