You are viewing a single comment's thread from:

RE: Engine Snapshot Stats

in Programming & Dev2 years ago

Nearly 60 gig is incredible. It's a good thing that mongo can unzip it in place rather than having to unzip it first and then read it to save the storage. It's already costing a pretty penny to host a fullnode for engine, even if we don't count the bandwidth to get the data out:

ss.png

Sort:  

Yeah unfortunately.. hopefully the restore_partial.js improves this (if not setting up a new node), but never actually had to use it myself.
One other option would be to restore from your local machine, but I guess that's a lot slower.

I've used restore partial a few times after divergence due to random reasons while experimenting, and it works beautifully. Setting up the new one is 100% where the problem lies for now. Hopefully we find more performance tweaks to improve that, or what I'd prefer, make syncing from a hived node faster so there's no need for snapshots.