You are viewing a single comment's thread from:
RE: Steem Pressure #3 - Steem Node 101
Hello. Thanks for the Steem Pressure series so far.
I'm investigating setting up a local node to generate a local copy of the steem blockchain to in turn create a database. I had initialy tried using steem python to generate a .json file of the blockchain using the public api, but that was evidentaly not ideal due to the time it would take to complete. Would you be able to give me an idea of the hardware, and the node plugins, that would be required to achieve this? I have so far not came accross a tutorial which provides instruction as to this, and would be greatful for any help you could provide.
Yes, definitely having a local steemd node will improve performance of such data gathering. As for configuration/plugins needed it all depends on which API calls you will be using to get that you need.
In worst case it would be a "full node" i.e. one with full bells and whistles (there should be some post about it where I provided my config for a full node, it's old but no much things have changed).
However, it's possible for you to optimize the config by choisng only those plugins you need (or maybe even ops filtering for account history).
Full node can currently run with 128GB RAM (or even 64GB) if you have very fast storage backend (for swap), but the more RAM, the faster your node will be able to answer your requests.
Thanks for taking the time to answer :) What I had in mind would require a record of all transfers from and to an account as well as rewards received as a minimun.
I'm not sure if this is something you may have tried, but what would be the likely result of trying to run a full node with less RAM (perhaps 32GB or 16GB)? Would the node fail to run, or would it just be much slower?
It would so slow that at some point it wouldn't be able to process blocks faster than they are coming, spending all its time on I/O operations.