You are viewing a single comment's thread from:

RE: [Docker compose] How to run a hived node / seed node / witness node

in HiveDevs3 months ago (edited)

About system requirements: not sure how much ram is needed but I run node on machine with 4 gigabytes (maybe 32 gigabytes is for building hive from source. Also if you have limited disk space - you can run smth like "pruned" node in bitcoin - don't store all block log at all or store only 1milion last blocks. To run "pruned" node you must add "block-log-split = 0" (or "block-log-split = 1" for one milion blocks in storage) in config.ini. Massive sync from 0 takes like 1-2 days nowadays. It should be possible to run node on raspberry pi with external ssd like 50gigs, not tested this thought raspberry pi is ARM not sure if this will work smoothly. But for full block_log it takes like 1TB.

Sort:  
 3 months ago  

I edited the requirements with more info.


@mahdiyari Is a server with 1TB enough to run a witness node or it needs more space? Asking because I see this in the Hive docs:

4TB of NVMe or SSD is kind of high...

 2 months ago  

This post is about just a hived node. Which is a witness/seed node. The screenshot covers HAF and Hivemind too. Those are separate software that offer more APIs to the interfaces like peakd and ecency.

Great! So I can get away with a 1TB hard drive to run the witness node?

 2 months ago  

Yes

 3 months ago  

You are right. It should be possible to run hived on lower end machines with pruned block_log.

I should have probably mentioned that as well. Thanks.

I remember not being able to run hived with 8gb of ram but I think that was building from the source. I didn't think about it that much as with this one I was aiming for seed nodes and I don't think running a public seed node without the block_log would be that beneficial. But for other uses, it is valid.