My last proposal has run out almost a year ago on May 31st 2024, so over the past year I've been running the snapshot servers from savings. This proposal will be used for covering costs of running the engine snapshot servers over the next year and for covering the costs of upgrading storage, which I had to do recently.
Currently I am running two servers for creating daily snapshots of the hive-engine sidechain, one for full nodes and one for light nodes. The size of light node snapshots is pretty stable at around 6GB, as they only contain the history of hive-engine blocks and transactions for the past 30 days.
The size of full node snapshots on the other hand is increasing with an almost constant rate of 140MB per day and has reached a size of 218GB.
So what this proposal is covering:
- Server for creating Full Node snapshots
- Server for creating Light Node snapshots
- Storage for providing the snapshots
For my last proposal I was asking 50 BEE daily (~7$). Because of the increased storage and decreased value of BEE/HIVE, I am now asking for 85 BEE daily, of which the first half will be used for covering server costs and the remaining half will go into savings to cover additional upgrades / costs and fluctuations of BEE/HIVE over the next year. That's again ~7$ daily, so about the same as the last proposal.
You can vote for the proposal (with staked WORKERBEE) over here: https://tribaldex.com/tokenfunds/BEE:WORKERBEE
Vote for my HIVE witness using Keychain.
Have you considered using S3 compliant service to store the outputs? Might be cheaper than renting a server for it.
Thank you, I need a strong server and at least 1TB for the full node anyways, as the running node now requires about 500GB and for keeping up with the chain, especially since ivm is a little bit slower than vm2 used to be. But I might consider this in the future when storage requirements change🙂
Ouch, seems to have grown quite a bit since I stopped running mine, think it was at the low 400s. That’s some quick growth.
should be around 150MB a day
Is that the snapshot or the actual node itself?
Haven't really tracked the node size so far, but I'm guessing it's 1.5 to 2 times as much. Probably depends on compression level and stuff.
Would be interesting data for sure.
Have you also considered running a read replica off your node that runs api.primersion.com and then just using that to take the snapshots so you don’t need an as powerful server?
But I would still have to shut down the node for taking the snapshot, so the data does not change in the meantime, right? Or is it possible to pause replication?
Ah yeah I forgot that's needed. Might be a way to pause replication, I don't work with mongo enough to know the answer of the top of my head.
at least for the snapshot. probably a lot more for the running instance.
I would love to help you out on this one, but workerbee is one of the few tokens I don't hold! However, you still have my witness vote!
No problem - thank you for your support🙂
Congrats man, keep on running!
Congratulations @primersion! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next payout target is 22000 HP.
The unit is Hive Power equivalent because post and comment rewards can be split into HP and HBD
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOP