From: Daniel F <nanotube@gmail•com>
To: bitcoin-development@lists•sourceforge.net, fg@numlog•fr
Subject: Re: [Bitcoin-development] Running a full node
Date: Sat, 08 Nov 2014 10:28:16 -0500 [thread overview]
Message-ID: <545E3690.2060908@gmail.com> (raw)
In-Reply-To: <545B44AA.7030107@numlog.fr>
> But I'd like to know what storage, RAM and bandwidth resources are
> needed. I guess that the problem is not the CPU.
Hi Francis,
Here are some rough guidelines for you, based on the statistics from my
node:
disk usage: about 30GB currently for the blockchain data. It'll only
keep growing from here, but relatively slowly.
cpu usage: pretty much nothing, after you have synced the blockchain.
ram usage: after it runs for a few months, my node gets up to using 1.5
GB of ram or so.
bandwidth usage: my node averages about 500GB of traffic per month, most
of it outgoing.
Hope that gives you a rough idea of what you can expect for running full
node.
Best,
Daniel
next prev parent reply other threads:[~2014-11-08 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 9:51 Francis GASCHET
2014-11-06 11:09 ` Thomas Zander
2014-11-06 21:38 ` odinn
2014-11-08 15:28 ` Daniel F [this message]
2014-11-08 17:44 ` Melvin Carvalho
2014-11-08 21:47 ` Jameson Lopp
[not found] <545B5323.3000403@numlog.fr>
2014-11-09 15:22 ` Francis GASCHET
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545E3690.2060908@gmail.com \
--to=nanotube@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=fg@numlog$(echo .)fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox