You are viewing a single comment's thread from:

RE: Introducing: Steem Pressure #1

it's great to read this article I was actually looking at running a seed node to build a bit of SP. I've followed the quickstart guide and managed to have a steemd running for the last hour

steemit/steem "/bin/sh -c /usr/l..." About an hour ago Up About an hour 0.0.0.0:2001->2001/tcp, 0.0.0.0:8090->8090/tcp steemd-exchange

I've not really pay attention to the hardware requirements since I'm doing that with my laptop, I'm doing it to explore steemit and understand.
I haven't look to much in the cli_wallet I don't really understand the use of it yet what is it for ?
What are the motivations behind running a node ? I mean if you serious about it you obviously spend money in proper hardware.
How many nodes are running all together ?
What should I do give up or leave my laptop running ? it's very silent it can run all night no problem.
I have 8Gb of ram but right now ony 3.2GB is used and that's probably my OS, is that mean something is not working or that the syncing is still processing ?
thank you for this article I felt a bit isolated with this cheers

Sort:  

Most likely it's still syncing, or at least trying to sync. Other than for educational purposes or development, there's no point for running steemd on your laptop. It would not help the network as a p2p node because of most likely high latency and poor connectivity (unless your laptop is quite powerful one with FTTH uplink or so).
cli_wallet can let you manage your wallet from the command line, execute some other commands like voting for me as a witness: vote_for_witness blacksheepblog gtg true true.

thank you for the advice, would it be a way for me to see a overall page with steemit nodes connected or some stats for each nodes I might be able to see my latency ?

As soon as your node would start receiving blocks in real time (after initial sync) you would get an info about latency, something like:

3030177ms th_a       application.cpp:514           handle_block         ] Got 33 transactions on block 19056032 by gtg -- latency: 177 ms
3033119ms th_a       application.cpp:514           handle_block         ] Got 37 transactions on block 19056033 by riverhead -- latency: 119 ms
3036482ms th_a       application.cpp:514           handle_block         ] Got 40 transactions on block 19056034 by xeldal -- latency: 482 ms
3039615ms th_a       application.cpp:514           handle_block         ] Got 31 transactions on block 19056035 by thecryptodrive -- latency: 615 ms
3042122ms th_a       application.cpp:514           handle_block         ] Got 50 transactions on block 19056036 by smooth.witness -- latency: 122 ms