Daemon much slower than CLI for starting nodes about storjshare-daemon HOT 3 CLOSED

Can you share the method you are using to start your nodes?

from storjshare-daemon.

Bash script that functionally issues a bunch of:

storjsjhare start -c /storj/nodexx/config

commands.:

storj@fs2 ~ $ cat storj.begin
storjshare killall
sleep 10
storjshare start -c /storj/node000/config
storjshare start -c /storj/node001/config
storjshare start -c /storj/node002/config
storjshare start -c /storj/node003/config
storjshare start -c /storj/node004/config
storjshare start -c /storj/node005/config
storjshare start -c /storj/node006/config
storjshare start -c /storj/node007/config
storjshare start -c /storj/node008/config
storjshare start -c /storj/node009/config
storjshare start -c /storj/node010/config
storjshare start -c /storj/node011/config
storjshare start -c /storj/node012/config
storjshare start -c /storj/node013/config
storjshare start -c /storj/node014/config
storjshare start -c /storj/node015/config

from storjshare-daemon.

Ah, so reason it is taking so long is because each command is establishing a new connection to the daemon, sending RPC, daemon receives and validates config, forks share process, responds to RPC, then closes connection. There is also a short artificial delay between the beggining of this and end to ensure the connection to the daemon is opened and closed cleanly.

The best way to start a series of nodes is to get them all running as you like and then running storjshare save to create a snapshot. This will let you later resurrect all the shares with one command storjshare load which eliminates the latency added by running each command separately. It will fork N shares with a degree of parallelism until all are running.

from storjshare-daemon.