You are viewing a single comment's thread from:

RE: SteemWorld ~ Weekly Support ~ #5

in #steemworld6 years ago

Do you need to maintain your own witness when you can send API calls to any other witness node? Seems like you have a large room for cost optimization.

Sort:  

There are 3 kinds of nodes (seed, witness, RPC). For executing API calls on my own server I would need a (full) RPC node. If I should become a top witness in future, I will start my own RPC node. The required hardware for running such a node is very expensive (would need at least 256 GB RAM (better more) ~ $240/month on privex.io + $200 setup fee).

One of the next steps for me is starting my witness node. Since we now/in near future need a 64GB RAM machine + 240GB SSD + extra server for the seed node, it's not super profitable currently, but maybe I will receive enough votes to reach the top 50 fast.

My costs are really at minimum and I don't think that I can really optimize them. The rent for my tiny apartment is ~ 240€/month (including warm water, heating etc.) I'm currently living a very minimalists life...

Why don't you use any other RPC node?

Also, carefull highload optimisation could make miracles. You could forward RPC requests to remote RPC node (zero costs for maintaining) and caching them on fast Redis DB. So you could lower you hardware costs dramatically without raising latency for 98% of users.

Why don't you use any other RPC node?

That is what I do. You can choose the node you want to use in settings on SteemWorld. But RPC nodes don't come with all features which I need in my tool. Mentions, follower history, incoming delegations, delegation history, transfer and content searching in posts, comment counts, witnesses produced block ratio, voting stats and many more things are only possible by parsing the chain by myself and storing the data in a fast db on my own servers.

Of course it is possible to develop own API calls, but that would require to run an own full node.

mmm... SteemSQL?