You are viewing a single comment's thread from:
RE: @ned - are we on the verge of a Steemtrain wreck? Answer NO - BUT THERE ARE STILL VALID CONCERNS
Hey there @gtg, I'd love it though if you would make a tutorial maybe on making a Full API node in best practices?
I use your node for my upcoming app, so it would be nice to make a few more for some load balancing and etc.
If I would have time for that...
Actually this is pretty straightforward, as long as you are not expecting to run it on potato-grate hardware ;-)
Also, a lot depends on certain needs. Not all the people needs really full node with all plugins. Most of people doesn't. Like for example exchanges mentioned by that troll are not using full nodes.
Most info needed to successfully run your node is in docs. You might want to modify that depending on your exact needs. Feel free to catch me on steemit.chat as Gandalf but expect some delays with answers.
I would gladly help with setting up public nodes.
BTW, I'm able to have considerably low amount of RAM mostly because I have decent speed on my storage backend. Current setup is very cost effective, however I'm running out of space (storage is fast but small, as I have 3 disks combined)
Ah, so instead of having 128GB RAM, you're using SSDs in RAID 5 for your swap backend?
RAID1
Of course having 128GB of RAM to keep there everything would be nice, but not cost effective.
I very much appreciate your extra clarity on this issue, but it does sound to me like that architecture won't scale beyond a few months without major work. I hope there are plans in place, and that Steem Inc. can communicate better on this issue in future.
Thanks again though!