3 ms·
> one issue I’ve experienced with running an IPFS node is that it can use quite a bit of bandwidth, just for making the network work (not even for serving your
by e12e 7y ago
> one issue I’ve experienced with running an IPFS node is that it can use quite a bit of bandwidth, just for making the network work (not even for serving your content!). This has been greatly mitigated with IPFS 0.4.19, but my Azure VMs are still measuring around 160GB/month of outbound traffic (it was over 400 GB with IPFS 0.4.18).
I'm not sure if that's 160gb/vm or 160gb across all vms - but either way that's 10-30 usd/month in bandwidth?
Pretty steep compared to a (single) 5usd/month vm or free (free tier of cdn provider).
Interesing write-up, though. Nice to see cf support ipfs.
- Scoundreller 7y agoI wonder why EC2 bandwidth costs so much more than s3 bandwidth (and the same equivalent questions for Azure).
- Turbots 7y agoThose are the fun, hidden costs nobody thinks about upfront, most people usually only calculate compute and storage, but forget about ingress/egress costs. It isn't that much usually, but it all adds up.
- momack2 7y agoDefinitely check out the latest version: https://blog.ipfs.io/054-go-ipfs-0.4.22 https://blog.ipfs.io/054-go-ipfs-0.4.22 - significant bandwidth improvements since 0.4.19 and more coming in the next minor release too!